Deployment · Early access

Run Code Swan Entirely
Inside Your Own Perimeter

Deploy Code Swan on your own clusters, using your own LLM keys. Your source code and metadata never leave your network. It is the full product, in your environment, under your controls, built for teams whose code simply cannot go anywhere else.

What stays inside your network

  • Runs on your own clusters, in your own cloud account
  • Scanning uses your own LLM keys and your existing provider contract
  • Your source code never leaves your network
  • No repository data is sent to Code Swan, ever
  • Authenticates through your own identity provider (SSO / SAML)
  • The same catalog and product as the cloud, nothing held back

Why teams choose self-hosted

For security-conscious and regulated teams, where the code lives is not a preference, it is a requirement. Self-hosted meets it without giving anything up.

Your Clusters, Your Control

Code Swan runs entirely inside your own infrastructure. There is no outbound connection to us, no data leaving your perimeter, and nothing for your security team to take on faith. The whole system lives where your code already lives.

Bring Your Own Model

Scanning runs on your own LLM keys and your existing provider contract, whether that is a hosted API or a model inside your own network. You keep control of spend, data handling, and which provider ever sees your code.

Built for Data Residency and Compliance

When source code cannot leave a network for legal, contractual, or regulatory reasons, self-hosted is the answer that lets those teams adopt Code Swan at all. Data stays in your region, under your controls, inside your audit boundary.

The Full Product, Nothing Held Back

The living catalog, architecture graph, API intelligence, cloud topology, semantic search, and MCP server are all present. Self-hosted is a deployment choice, not a stripped-down tier.

How it works

Three steps, all inside your own environment.

Deploy to your cluster

Code Swan runs in your own cloud account. We work with your platform team to stand it up inside your existing environment.

Connect your repositories

Grant read-only access to your version control. Repositories are scanned in place; only metadata is built, and it stays with you.

Point it at your LLM keys

Bring your own model provider and keys. Scanning runs on your contract, so your code is only ever seen by the provider you already trust.

Frequently Asked Questions

What does self-hosted deployment include?

The complete Code Swan product, running inside your own infrastructure: the living software catalog, architecture graph, API intelligence, cloud resource topology, semantic search, and the MCP server. It is the same product as our cloud offering, deployed in your environment rather than ours.

Does our source code ever leave our network?

No. In a self-hosted deployment, Code Swan runs on your own clusters. Repositories are scanned in place, only metadata is kept, and no repository data is sent to Code Swan. Your source never leaves your perimeter.

Can we use our own LLM provider and keys?

Yes. Scanning runs on your own LLM keys and your existing provider contract, whether that is a hosted API or a model running inside your own network. You keep control of which provider ever processes your code, and of the associated spend.

What infrastructure is required to run it?

Code Swan runs on your own clusters in your cloud account. The exact shape depends on your environment, so we work with your platform team on the deployment during onboarding. Reach out and we will walk your team through the requirements.

How is self-hosted deployment priced?

Self-hosted is part of our Enterprise offering and is not priced per seat on the pricing page, because the shape of the deal depends on your environment. See the pricing page for the deployment options, or talk to us for a quote.

Does self-hosted help with our data-residency or compliance requirements?

It is designed for exactly that. When source code cannot leave a network for regulatory, contractual, or data-residency reasons, running Code Swan inside your own perimeter keeps everything within your region, your controls, and your audit boundary.

Keep everything in your own perimeter

Talk to us about a self-hosted deployment, and we will walk your platform and security teams through exactly how Code Swan runs inside your environment.