Your integration is built. Now keep it running.
Most API integrations do not fail loudly. They fail quietly, at 2 a.m., when a token expires or a vendor ships an API update, and nobody notices until the data is already wrong. INSIDEA hosts your integration, watches it every day, and fixes it before it becomes your problem.
The integration is the easy part.
We build and test most API integrations in two to three weeks. Then the project stops, and it usually stops in the same place: the code needs somewhere to live.
Nobody internally owns hosting
The question bounces between engineering, IT, and operations for weeks because it was never anyone's job. The build is finished and the value is still sitting in a repository.
The approval chain outlasts the build
IT wants a security review, procurement wants a purchase order, and the integration we shipped in three weeks waits two months for a server it could have had on day one.
No one wants to grant deployment access
The server exists. What does not exist is a person willing to be the one who approved external access to it. That is a reasonable position, and it stops projects cold.
It goes live somewhere unofficial
A spare instance, a developer's account, a machine nobody documented. It works for six months, then a token expires and there is no one watching the logs.
None of this is a technology problem. It is an ownership problem, so we removed it.
Host it yourself, or let us handle it.
Every integration we build comes with a maintenance and support plan. You choose where the code runs.
Your infrastructure
We deploy to your servers and maintain the integration from there. You keep full control of the environment, provide deployment access, keep the environment patched, and give us a technical contact for anything infrastructure related.
INSIDEA infrastructure
We host the integration on managed cloud infrastructure we own end to end, included in your plan. No internal approvals, no IT ticket, no server for your team to babysit. The integration goes live in days rather than weeks.
Simple, monthly, cancel anytime.
All plans are month to month. No annual contract, no setup fee, no lock-in. Every plan covers one integration. If you run more than one, each gets its own plan, and we will price them together.
- Covers one integration
- Weekly error log review
- Critical response in 1 business day
- Standard response in 2 business days
- API version updates and credential refresh
- Monthly health summary
- Business hours support, ET
- Staging environment available as an add-on
- No named technical contact
- Covers one integration
- Daily error log review
- Critical response in 8 business hours
- Standard response in 1 business day
- API version updates and credential refresh
- Staging environment included
- Monthly health report
- Business hours support, ET
- No named technical contact
- Covers one integration
- Continuous monitoring with alerting
- Critical response in 4 business hours
- Standard response in 1 business day
- API version updates and credential refresh
- Staging environment included
- Monthly report and quarterly review call
- Named technical contact
- Extended hours support, ET
All prices in USD. Additional hours beyond your plan are billed at $75 per hour. Unused hours do not roll over. Upgrade or downgrade at any time, effective from your next billing cycle.
| Compare plans | Essential | Growth | Scale |
|---|---|---|---|
| Monthly price, per integration | $300 | $500 | $1,000 |
| Maintenance hours per month | 3 | 6 | 10 |
| Hosting, SSL, and backups | Included | Included | Included |
| Error log review | Weekly | Daily | Continuous, with alerting |
| Critical issue response | 1 business day | 8 business hours | 4 business hours |
| Standard request response | 2 business days | 1 business day | 1 business day |
| API version updates | Included | Included | Included |
| Staging environment | Add-on | Included | Included |
| Health reporting | Monthly summary | Monthly report | Monthly report and quarterly review |
| Named technical contact | Not included | Not included | Included |
| Support coverage | Business hours, ET | Business hours, ET | Extended hours, ET |
What you are actually paying for.
Hosting and infrastructure
Managed cloud hosting for your integration, SSL certificates, automated daily backups, and environment security patching. Tell us your data residency requirements at scoping and we confirm the region in writing before deployment.
Proactive monitoring
We review error logs on your plan's schedule and check that data is syncing as expected. You hear about problems from us, not from a sales rep wondering why deals stopped appearing in HubSpot.
Maintenance and fixes
Bug fixes, failed sync recovery, credential and token refreshes, and API version updates when a vendor changes their specification. This is what your monthly hours are for.
Health reporting
A monthly report covering sync volume, errors caught and resolved, and hours used. You always know what the subscription is buying you.
The team that built it
No ticket queue and no anonymous first line. You reach the consultants who wrote your integration and know why it was designed the way it was.
Scope discipline
If a request falls outside your plan, we tell you before we do the work, not after. You get a scope and a price, and you decide.
What is not included.
We are specific about this so there are no awkward invoices later. The following sit outside your plan and are quoted as separate work.
- New integrations, new endpoints, or new data objects outside the original scope
- New features, workflow changes, or logic changes requested after go-live
- Full rebuilds when a vendor deprecates an API entirely, as opposed to routine version updates
- Custom dashboards, reports, or analytics builds
- Data migration or historical data backfills
- Third-party software, app marketplace, or platform license fees
- Changes to your own systems, or issues caused by them
- Any request that exceeds your plan's monthly hours
From signature to live in days.
Choose the path
Your infrastructure or ours. We settle this before development starts, so the project never stalls at handover.
We deploy
Your integration is deployed, tested in staging where your plan includes it, and moved to production.
We monitor
Automated checks and scheduled log reviews start immediately. Your first health report lands at the end of month one.
We maintain
Fixes, updates, and improvements inside your monthly hours. Anything larger is scoped and quoted before we start.
HubSpot Accreditations
Five partner-tier credentials HubSpot itself uses to vet implementation depth.
What happens if you cancel.
Your integration runs on INSIDEA infrastructure for as long as your subscription is active. We put this in writing on the page rather than in a clause on page nine, because an integration stopping is not something anyone should discover after the fact.
- The integration stops running
Data stops syncing between your systems on the day your subscription ends. Plans are month to month, so cancelling takes 30 days' notice.
- Your environment is held for 30 days
You can reactivate at any point in that window without a rebuild and without losing your configuration.
- You can take it with you
Within that window we package the code, deployment documentation, and configuration so you can move the integration onto your own server. Handover is a one-time service.
- Then the environment is decommissioned
After the retention window the environment and any data held in it are securely removed, and we confirm it in writing.
For plans hosted on your own infrastructure, the code stays on your server. What ends is the monitoring, maintenance, and support.
Not built yet?
This page is about keeping an integration alive. If yours does not exist yet, start with the build.
Custom HubSpot integrations
ERPs, billing platforms, data warehouses, legacy systems, and the middleware between them. Scoped before we quote.
Marketplace apps, configured
Salesforce, Stripe, Slack, Zapier, Zoom, Google Ads, Calendly. The connector exists; the outcome depends on configuration.
Questions we get asked.
Do we have to buy a maintenance plan?
Every integration we deliver ships with one, whether it runs on your infrastructure or ours. The reason is what happens without it: an API integration does not fail loudly, it fails quietly at 2 a.m. when a token expires or a vendor changes a specification, and nobody notices until the data is already wrong. The plan is how we make sure what you paid us to build keeps working. If your team wants to operate it themselves, we will scope a handover instead and tell you exactly what you are taking on.
We already have a server. Do we pay less?
The plan price is the same, because hosting is the smaller part of what the plan covers. Monitoring, error log review, fixes, and API version updates are identical work whether the integration runs on your infrastructure or ours. What changes is who carries the server cost, the patching, and the access management. Most teams look at that and choose INSIDEA hosting, and we are happy either way.
What counts as one integration?
One connection between two systems, covering the endpoints and data objects defined in your original scope. Connecting HubSpot to your ERP is one integration. Adding a second connection to your billing platform is a second integration and needs its own plan. If you are running several, tell us and we will price them together.
Do unused hours roll over?
No, hours reset monthly. If you consistently use fewer hours than your plan includes, tell us and we will move you to a lower tier. We would rather you paid for what you use than quietly overpaid.
What if we need more hours in a given month?
We tell you before you hit the limit, not after. Additional hours are billed at $75 per hour. If you are running over most months, moving up a tier is the better answer, and we will say so rather than quietly billing the overage.
Can we change plans?
Yes. Upgrade or downgrade at any time, effective from your next billing cycle.
Where is our data hosted?
Your integration runs on managed cloud infrastructure with region options available. Tell us your data residency requirements during scoping and we confirm the region, the backup retention period, and the compliance posture in writing before deployment.
Is this a HubSpot requirement?
No. This is an INSIDEA service for custom API integrations. It is separate from your HubSpot subscription and from any app marketplace fees.
How quickly can we go live?
Once your integration is built and you have chosen INSIDEA hosting, deployment typically takes two to three business days. On your own infrastructure the timeline depends on how quickly your team can grant access.
What happens to the integration if we cancel?
It stops running when the subscription ends. We hold the environment for 30 days so you can reactivate without a rebuild, or we package the code, documentation, and configuration so you can move it to your own server. After that window the environment is securely decommissioned.
Stop losing weeks to the hosting question.
Your integration should go live the week it is finished, not the month after your IT team gets around to it.
How INSIDEA works
