Native integrations vs iPaaS vs custom code
Native integrations vs iPaaS vs custom code is a choice between three ways of making two programs share information. A native integration is a ready-made connection that comes with your software. An iPaaS is a separate online service that sits between two programs and passes information along. Custom code is a connection a programmer writes just for you. The right choice depends mostly on who should look after the connection later.
Why this matters to a business
Say your online shop takes an order and your accounting program needs to know about it. Either someone types the order in again, or the two programs are connected. Such a connection is called an integration. It saves the typing. But like a car, it needs someone to look after it.
The three options in plain words
- Native integration. You click "connect" inside your software and sign in to the other program. The software maker built the connection and repairs it when something changes.
- iPaaS. The name is short for "integration platform as a service". It is a third product in the middle. There you set up rules such as: when a new order arrives in the shop, add it to accounting.
- Custom code. A programmer writes a small program that does exactly what you ask. It is yours, and so is the job of keeping it running.
| Native | iPaaS | Custom code | |
|---|---|---|---|
| Who sets it up | You, with a few clicks | You, rule by rule | A programmer |
| Who repairs it | The software maker | Partly the service, partly you | You |
| Time until it works | Minutes | Hours | Days to weeks |
| Extra cost | Usually none | One more subscription | The programmer's time |
Which one for which job
- Email, calendar and payments: native. These are standard, and most business software offers them ready-made.
- Two programs that do not know each other: an iPaaS. It is the quickest way to find out whether the connection is worth having.
- A special program that only your trade uses: custom code, written by someone you can still reach in two years.
- A long chain across many programs: think twice. Every link is a place where the chain can break. It may be a sign that those steps belong in one program.
Three questions before you connect anything
- Who notices when it stops? A connection can fail quietly, and weeks can pass before anyone sees it.
- Which side is right? If both programs hold the same customer address, decide which one counts.
- Who looks after it? Write down one name, and a stand-in.
Do you have to pick only one?
No. Most small companies end up with a mix. Native connections for the standard programs, an iPaaS for a gap or two, and custom code for a rare special case. The aim is to keep the number of connections small and to give each one a person who looks after it.
How Worknano handles this
Worknano covers two of the three options inside the workspace. It comes with native connections that the Worknano team maintains, among them Google Workspace and Microsoft 365, Slack and Microsoft Teams, Stripe and PayPal, QuickBooks and Xero. For other software, a visual integration builder lets you set up a connection on screen, without a programming project. A failed transfer can be run again, each connection has its own limited access, and every exchange with an outside program is logged. Between CRM, projects, finance and files no connection is needed at all, because they share one database.
Create a free workspace and connect the first tool you want to keep.