# Run the aixplain OS on your own servers

By default, the aixplain OS runs on cloud and you use it at app.aixplain.com. Organizations whose data must stay inside their perimeter can run the same OS on their own servers: on-prem, in their own VPC, fully air-gapped, or in a cloud in their region. This article explains what you get, what an install needs, how the first two weeks work and how to get started. For the full picture, see **[aixplain for enterprise](https://www.aixplain.com/enterprise)**.

> Running the aixplain OS on your own servers comes with the **[Enterprise](https://www.aixplain.com/enterprise)** plan, priced to your deployment. Book a demo to size it with our team.

## What you get

The same aixplain OS you use on cloud, inside your perimeter:

- **An organization workspace:** members and roles, policies, a budget and approvals, set once for the whole organization.
- **A workspace per team:** each department, from finance to IT, gets its own workspace with its own access policies and budget. What one team builds, every team can use.
- **The control panel:** inspectors check every input, step and output; the dashboard shows every run step by step with its cost; the audit log records who did what, under which policy.
- **Omni and Koder for everyone:** every employee hands work to Omni, and every developer builds with Koder. aixplain Desktop goes on each person's computer and connects to the OS on your servers.
- **Agents as secure APIs:** your customers reach your agents in your app, on WhatsApp or on your website, each agent behind its own key, budget and tracing.
- **Your models and data:** any model in the Marketplace, open-source models you host, or your own, plus your systems connected as tools that keep the access rules you set.

## Where it can run

| Where | What it means |
| --- | --- |
| **Your VPC** | The OS runs in your own cloud account, connected to the outside only as you allow |
| **On-prem** | The OS runs in your own data center |
| **Air-gapped** | The same OS with no outside connection. Nothing calls outside your network |
| **A cloud in your region** | Our cloud or a partner's, in the region your rules require |

The same agent runs in any of these, and its full definition exports as JSON, so you can move it later with nothing to rebuild.

## What an install needs

The aixplain OS runs as Linux containers on CPUs, behind your load balancer, with data storage included. You need GPUs only to host your own models. We size it with you, install it once your servers and security approvals are ready, and patch it on a schedule agreed with you.

> **Note:** In air-gapped mode, nothing calls outside your network. Models and tools you host on your servers use no credits; you add usage credits only when aixplain connects you to cloud models and tools.

## Your first 14 days

Start with one team rather than months of mapping workflows. The clock starts once your servers and security approvals are ready.

1. **Day 1, size:** tell us the size of the team and the work, what it connects to and where it runs. Pick any model, Arabic ones included, and swap it anytime.
2. **Day 5, deploy:** we put the aixplain OS live on your servers with your team, connected to your systems, with policies, budgets and an audit trail on. Your first team gets Omni and hands it real work that day.
3. **Day 10, create:** teams create their first agents with Omni and share them, with every step recorded. Your developers start building an AI service with Koder.
4. **Day 14, prove:** your first agents and first AI service are live, each with an owner, a budget and a record of every run. Measure the work done, the time saved and the cost of every run, then scale to the next teams.

## Your data

On your servers, your data stays there. When an agent uses a cloud model, the request goes to that model's provider. In the Marketplace you can pick models with zero data retention or hosted in your region, and a policy can limit an agent to in-country models. For how we handle data, see **[Privacy and data](https://www.aixplain.com/support/articles/privacy-and-data)** and **[Security](https://www.aixplain.com/security)**.

## Start on cloud, move later

You can start on cloud and move to your own servers when you're ready. Your agents and workspace move too, with no rebuild. Swap a model and an agent keeps its owner, policies, inspectors and run history; move it and it keeps its tools and API.

## Frequently asked questions

### Do my people use a different app on our servers?

No. They use the same Omni, Koder and aixplain Desktop. Desktop connects to the aixplain OS on your servers instead of to app.aixplain.com.

### Can we keep working if a model provider fails?

Yes. Set a fallback for each model. On your own servers, nothing depends on an outside service.

### How do we control spend?

Budgets per workspace, key and model stop an agent before it overspends, and every run shows its cost.

### Can agents we already run be governed too?

Yes. Bring them in as tools over MCP or an API, and they get the same inspectors, approvals, budgets and records as the agents you build on the aixplain OS.

## Get started

- **Book a demo:** a 30-minute session on your use case, where it runs, who controls it and what it costs. **[Book a demo](https://www.aixplain.com/contact?reason=demo)**.
- **Send your security questionnaire:** see **[Security](https://www.aixplain.com/security#security-contact)**.
- **Read more:** **[aixplain for enterprise](https://www.aixplain.com/enterprise)** and our guide to **[running agents air-gapped](https://www.aixplain.com/guides/copilot-studio-alternative-air-gapped)**.