IAToolkit Self-hosted

The same platform, on your infrastructure.

For when infrastructure control is a requirement rather than a preference. Your team deploys, updates, and operates IAToolkit inside your perimeter, with an annual licence and an agreed support scope.

When it makes sense

Self-hosted is not for everyone, and that is fine.

Hosted covers speed and simplicity for the large majority. Self-hosted exists for the cases where infrastructure is not negotiable.

Regulatory requirement

Sectors where data and its processing must stay inside a jurisdiction or a specific network, with evidence of where every component runs.

Your own platform team

Organisations able to operate their stack: deployments, upgrades, backups, and monitoring under their own standards.

Deep integration

When IAToolkit has to live alongside systems that will never leave the internal network, not even through an outbound connection.

Hosted or self-hosted

Same operating layer, different responsibility.

The capabilities are identical: private MCP, Secure Bridge, governed agents, monitoring, analytics, and operations console. What changes is who operates the infrastructure and how it is billed.

Recommended to start

Hosted

The managed way to run IAToolkit as your AI operations layer. We host the platform; your team connects AI clients through MCP, connects internal systems through Bridge, and monitors executions, usage, errors, and cost from the console. From US$249/month, with 10 users and US$50 of execution included.

For platform teams

Self-hosted

Annual licence on your own infrastructure. Your team deploys, updates, and operates. Support and guidance scope defined in the contract.

FAQ

What people usually ask us.

How is Self-hosted quoted?

With an annual licence, not a monthly per-user fee. The price depends on the scope of the deployment and the agreed support level. Talk to us and we will prepare a proposal.

Are there feature differences with Hosted?

Not in the platform. Bridge, private MCP, agents through API, company isolation, and the operations console are the same. What changes is who deploys and maintains the infrastructure.

How is execution charged?

In Self-hosted it is not: execution runs on your own infrastructure with your own model credentials, so provider consumption is directly yours.

Can we start on Hosted and migrate later?

Yes. That is the usual route: validate the first use cases on Hosted and move the deployment when volume or requirements justify it.

Self-hosted proposal

Request a self-hosted proposal.

Share your infrastructure requirements and we will define the licence and support scope with you.

Request a proposal