Managed open source for air-gapped and FIPS environments
For sites with no route to the internet, OSStend delivers PostgreSQL, Kafka, RabbitMQ and more through an operator on your cluster, with supported charts and images.
45 minutes with an engineer: we review your workload and sketch the design.
- ✓Operated by AceMQ
- ✓Co-managed
- ✓Air-gapped
- ✓FIPS hosts
Air-gapped cloud and on-prem sites have no route to the internet, so software, patches and support have to reach them another way. OSStend co-manages the data layer there: an operator on your cluster, supported charts and images, and hardened editions for FIPS hosts, on infrastructure you own.
- PostgreSQL
- MySQL
- MongoDB
- Redis
- Valkey
- OpenSearch
- Kafka
- RabbitMQ
- AWS
- Google Cloud
- Azure
- Kubernetes
- OpenShift
- Prometheus
- Grafana
- Datadog
- Dynatrace
- Splunk
What changes when there is no internet
Everything a connected site pulls on demand has to be brought in on purpose: images, charts, patches and the way engineers reach the system. These points are settled in the cluster design you sign off.
| Concern | In an air-gapped site |
|---|---|
| Software delivery | Delivered through an operator on your cluster, with supported charts and images, on infrastructure you own. |
| Patches and versions | Long-term support builds with security fixes backported, applied on your change calendar and never forced. |
| Monitoring | Metrics and alerts are forwarded to your own tools, such as Prometheus or Splunk, instead of a separate console. |
| Engineer access for 24/7 operation | Agreed in the design step and recorded in the cluster design, since there is no direct path from outside. |
| Network and access controls | Yours. You keep the network, the identity provider and the audit trail. |
Service levels on infrastructure you own
Air-gapped delivery belongs to the co-managed tier. Because you own the infrastructure, the SLA is a response-time SLA, not an uptime SLA.
Response targets for the co-managed tier are set per plan and written into the contract. How the tiers differ is on service levels.
FIPS hosts and hardened editions
Where a host must meet FIPS requirements, OSStend provides hardened editions of the engines. FIPS 140 is a US standard for cryptographic modules, and validated modules are listed by NIST.
NIST maintains the Cryptographic Module Validation Program, which lists validated modules (checked 30 Oct 2026). Whether a given host and engine combination is covered is decided with the customer during the design step.
For RabbitMQ, AceMQ's FIPSMQ broker uses FIPS 140-2 and 140-3 validated cryptographic modules. For other engines, the FIPS position of each host and engine is settled in the design.
Engines in an air-gapped site
The same engines and the same engineers are available as in a connected site. Start from the engine you run.
- Managed Kafka and managed PostgreSQL on Kubernetes or OpenShift. See Kubernetes.
- RabbitMQ hosting, with Windows and FIPS hosts and federation or shovel to your other sites.
- Managed Redis or Valkey, managed MySQL, managed MongoDB and managed OpenSearch.
When it fits and when it does not
Air-gapped delivery is for sites where the isolation is a requirement. Where a connected, standard plan is allowed, it is simpler and cheaper.
Contact us if
- ✓The site has no route to the internet and the data layer has to run inside it.
- ✓A policy requires FIPS-capable hosts. The residency side is on data residency and sovereign deployments.
- ✓You need a named team on call for engines your own staff would rather not carry.
Not a fit if
- ✕The workload may run in a public cloud region. See bring your own cloud.
- ✕You want a free tier or a card sign-up.
FAQ
Can managed databases run in an air-gapped environment?
Yes, in the co-managed tier. The service is delivered through an operator on the customer's cluster with supported charts and images, on infrastructure the customer owns.
How are patches applied without internet access?
Long-term support builds carry backported security fixes, and upgrades follow the customer's change calendar. How updates are brought into the site is agreed in the design step.
Is FIPS supported?
Hardened editions exist for hosts that must meet FIPS requirements. What is validated and what evidence is available is confirmed with the engineer during the review.
Related pages
- DeploymentManaged databases: our cloud, yours or on-premManaged databases in OSStend's cloud, your AWS, Azure or Google Cloud account, or your data center. PostgreSQL, Kafka and RabbitMQ, run 24/7 by engineers.
- SecuritySecurity and compliance at OSStendOSStend security: private networking, your identity provider, your key management and audit trail, plus air-gapped delivery and FIPS hosts you control.
- Service levelsService levels: two tiers, a written SLAOSStend service levels: fully managed and co-managed tiers, what each one covers, who is on call and how incidents are handled, with a written SLA for each.
- KafkaManaged Kafka in your cloud or data centerManaged Kafka with the broker count, partition plan, KRaft, Connect and schema registry designed for your estate, run 24/7 in your cloud or your data center.
- PostgreSQLManaged PostgreSQL service and Postgres hostingManaged PostgreSQL service, compared: how to choose between RDS, Aiven, Crunchy Bridge, Neon and a tailored cluster run 24/7 in your cloud or ours.
- Deployment · Your data centerPostgreSQL on Kubernetes, managed by OSStendRun PostgreSQL on Kubernetes and Kafka on your own cluster, co-managed by OSStend through an operator with supported charts and images, 24/7.
Talk to an engineer about your isolated site
Bring the engines, the platform and the isolation rules. An engineer will review them with you and sketch the design in 45 minutes.
- ✓A design sketch for your workload, not a plan menu
- ✓A zero-downtime cutover path for what you run today
- ✓A price for that design, after the review