Knowledge Base/Advanced Topics/Enterprise Deployment

Enterprise Deployment

Configuring a deployment targetConfiguring a deployment target
Set up the servers you deploy to as reusable deployment targets.
Watch: the production readiness checklist

Enterprise customers can run CodeSky as an isolated cluster — inside their own network, with no traffic leaving the perimeter. This is about hosting the platform; deploying the apps you build is separate and simpler.

What ships

  • The backend API, the web frontend, and the platform-admin app, packaged as containers.
  • SQL Server (or PostgreSQL) for application data.
  • Optional Ollama containers for fully on-prem, offline code generation.

Identity and access

  • Pluggable auth: built-in JWT for a trial, SAML/SSO for production.
  • Map your identity-provider groups to CodeSky roles.
  • Control who can generate, who can administer, and who can manage billing.

Air-gap mode

  • The platform refuses to call external providers (Claude, Grok, Gemini, Groq) and falls back to Ollama exclusively.
  • Plan capabilities are computed locally, so nothing leaves your network.
  • Ideal for data-residency, compliance, or classified environments.

Is this for you?

  • Most teams don't need it — the hosted platform at codesky.ai covers building, previewing, and deploying your apps.
  • Self-hosting suits organizations with strict data-residency, compliance, or offline requirements.
  • If that's you, talk to us about a deployment plan sized to your environment.

FAQ

Is this the same as deploying my app?

No. This hosts the CodeSky platform itself. Deploying the apps you build is covered by the Desktop Editor deployment guides.

Can it run fully offline?

Yes — in air-gap mode it uses Ollama on-prem and makes no external calls.

How do users sign in?

Through your identity provider via SAML/SSO, with IdP groups mapped to CodeSky roles.

Was this article helpful?