About hecigo
hecigo is an integration lab operated by HECIGO TECHNOLOGY CO., LTD, a company registered in Ho Chi Minh City, Vietnam. We do exactly one thing: the layer in between.
A contractor takes a specification and returns a build. A lab starts from the position that nobody, including us, can quote a middleware build accurately before looking at real data, because every pair of systems fails in its own way and most of that lives in what the API docs never mention. So the engagement is gated rather than quoted up front, and the deliverables from a step you stop at are yours to keep.
We are a small team. We say so on purpose: the alternative is a capability deck that implies otherwise and a first invoice that discovers the truth.
An integration lab, not a contractor
hecigo does exactly one thing: the layer in between. A 20-to-200-person company usually has enough software already, and each piece does its own job well. What is missing is whatever makes them talk to each other, and no vendor takes responsibility for that part.
We work in gated steps, and every step has an exit. You pay a small amount, watch it run, and only then decide whether to continue.
Even so, every pair of systems fails in its own way, and most of it lives in what the API docs never mention. Nobody can quote accurately before looking at real data, not even the most experienced team. That is why discovery and a POC exist: so you don't have to take our word for it.
What a lab means here
- We are a small team
- We say so on purpose. The alternative is a capability deck that implies otherwise, and a first invoice that discovers the truth.
- We run this layer ourselves
- Most of what we know about failure modes came from operating our own integration infrastructure for months, not from reading API docs. The blog is where that gets written down, including the parts we got wrong.
- The stack is deliberately boring
- Nothing exotic, so another team can pick the system up without us. That is a condition of the handover promise, not a preference.
Where to go next
- Developer resources: the open-source n8n nodes and every machine-readable endpoint on this site
- Blog: mechanics and failure modes, including ours
- Contact: email, phone, address, enquiry form
- /about.md (this page as Markdown)