Inquir inside your perimeter
For integrators, hosting providers and companies that keep their data in-house: we install the platform on your servers, with the same CLI, MCP server, IDE and templates as in the cloud. We start with a pilot.
Last updated: 2026-10-18
- A control plane on several nodes
- Runners and data on your servers
- A pilot on your hardware comes first
The problem
The public cloud does not always fit
Some customers cannot send data and compute to someone else’s cloud: security requirements, contracts with their own clients, a data centre of their own. Hosting providers need a platform on top of their servers, not a resold one.
Building such a platform yourself means Kubernetes, an image registry, storage, networking, backups, monitoring, and a team to keep all of it running.
What we install
What we install
The same platform inquir.org runs on: container applications, functions, pipelines, databases on volumes, domains with TLS, logs and metrics, the CLI and the MCP server for coding agents.
The control plane runs on several nodes: Postgres managed by Patroni with a synchronous replica, a standby control-plane node, and leader election for the background controllers. Workloads run on containerd runners installed by a script on ordinary Linux servers and connected by a private WireGuard network.
The image registry, S3-compatible storage and backups run on your side too, so data and compute stay inside your perimeter.
Inside your perimeter
What your perimeter gets
A highly available control plane
Several control-plane nodes, Postgres with a synchronous replica (Patroni), leader election for the controllers.
Runners on your servers
containerd runners installed by a script; services are placed across them by resources and node labels.
Data inside the perimeter
The image registry, artifact storage, volumes and their backups live on your hardware.
Multi-tenancy
Workspaces, organizations and roles: separate customers for a hosting provider, teams and projects for a company.
Developer tools
The web IDE, the CLI, the MCP server for Claude Code, Cursor and Codex, application templates and inquir.yaml.
A hybrid option
If full on-premise is not needed yet, your servers can join as runners of our control plane; we scope this during the pilot.
Pilot
How a pilot goes
A call
We go through your goals, the perimeter requirements and the servers for the pilot.
Installation
We set up the control plane and runners on your servers and connect your domain and storage.
Pilot workloads
We move one or two real services and test deploys, node failures, backups and restores.
Decision
After the pilot we agree on scope, support and terms.
Limits
What we do not have yet
The platform has no FSTEC certification, and it is not in the Russian software register yet; applying to the register is in our plans.
A fully air-gapped installation is not available out of the box: it needs mirrors of images and packages, so we assess it separately.
If any of this is a hard requirement for your project, say so on the first call and we will discuss timelines honestly.
When it fits
Who it is for
When this works
- Integrators who roll out a development platform at a customer site
- Hosting providers who want to sell a PaaS on their own servers
- Companies that must keep data and compute inside their own perimeter
When to skip it
- You need FSTEC certification: the platform does not have it
- You need software from the Russian register today: we have only planned the application
FAQ
FAQ
Do you have FSTEC certification or an entry in the Russian software register?
No FSTEC certification. The platform is not in the Russian software register yet; we plan to apply. If either is a must for your project, tell us on the first call.
What servers do I need?
Ordinary x86-64 Linux servers; we run on Ubuntu. How many and how large depends on the load: a highly available control plane needs several nodes, and we size the setup together on the call.
Can it run without internet access?
Not out of the box: it needs mirrors of container images and packages inside the perimeter and changes how installation and updates work, so we assess it separately.
Who updates and supports the platform?
We do: we ship the updates and help roll them out. The support level is fixed in the contract.
Can I offer the platform to my own customers?
Yes, that is one of the scenarios for hosting providers: each customer gets their own workspaces and access. We agree the terms individually.
How much does it cost?
It depends on the number of servers and the support level, and we price it individually after the pilot. Start with an email to info@inquir.org.
Before the call
What to look at before the call
How the platform looks to developers, in the cloud version.