Enterprise
Run Kodine safely inside your organization.
Kodine Enterprise targets organizations that need guarantees that code and data stay inside their own infrastructure. It achieves this through a centralized configuration that hooks into your SSO and your internal AI gateway.
Getting started with Kodine Enterprise looks like this:
- Run an internal trial with your team.
- Contact us to talk through pricing and implementation options.
Trial
Because Kodine is open source and stores none of your code or context data, your developers can simply get started and run the trial themselves.
Data handling
Kodine never stores your code or context data. Everything is processed locally or sent straight to your AI provider via API calls.
So as long as the provider you use is one you trust — or you route through an internal AI gateway — Kodine is safe to use.
The one exception worth knowing about is the optional /share feature.
Sharing conversations
When a user turns on /share, the conversation and its related data are uploaded to the service that hosts our share pages at kodine.net.
That data is currently delivered via our CDN’s edge network and cached at the edge, close to your users.
For the trial, we recommend turning it off.
{ "$schema": "https://kodine.net/config.json", "share": "disabled"}Code ownership
Everything Kodine produces belongs to you. No licensing restrictions, no ownership claims.
Pricing
Kodine Enterprise is priced per seat. When you run your own LLM gateway, tokens are not metered by us. For more on pricing and implementation options, contact us.
Deployment
After the trial, when you’re ready to roll Kodine out across the organization, contact us to discuss pricing and implementation options.
Central Config
Kodine can be set up so the whole organization shares one central configuration.
That centralized config hooks into your SSO provider and restricts users to your internal AI gateway only.
SSO integration
The central config lets Kodine authenticate against your organization’s SSO provider.
In other words, Kodine gets its credentials for your internal AI gateway from the identity system you already run.
Internal AI gateway
The central config can also lock Kodine to your internal AI gateway exclusively.
Every other AI provider can be switched off, so all traffic flows through infrastructure your organization has approved.
Self-hosting
Our recommendation is to disable share pages so data stays within your organization — but we can also help you host them on your own infrastructure.
This is on our roadmap today. If it interests you, let us know.
FAQ
What is Kodine Enterprise?
Kodine Enterprise targets organizations that need guarantees that code and data stay inside their own infrastructure. It achieves this through a centralized configuration that hooks into your SSO and your internal AI gateway.
How do I get started with Kodine Enterprise?
Begin with an internal trial alongside your team — Kodine stores no code or context data by default, which makes trying it out straightforward.
After that, contact us to talk pricing and implementation options.
How does enterprise pricing work?
Enterprise pricing is per seat. When you run your own LLM gateway, tokens are not metered by us. Contact us for a quote tailored to your organization’s needs.
Is my data secure with Kodine Enterprise?
Yes. Kodine stores none of your code or context data; everything is processed locally or sent straight to your AI provider. Combined with central config and SSO integration, your data stays inside your organization’s infrastructure.
Can we use our own private NPM registry?
Private npm registries work with Kodine thanks to Bun’s native .npmrc support. If your organization runs one — JFrog Artifactory, Nexus, or something similar — make sure developers have authenticated before launching Kodine.
To authenticate against your private registry:
npm login --registry=https://your-company.jfrog.io/api/npm/npm-virtual/That writes your credentials to ~/.npmrc, which Kodine picks up automatically.
Or configure .npmrc by hand:
registry=https://your-company.jfrog.io/api/npm/npm-virtual///your-company.jfrog.io/api/npm/npm-virtual/:_authToken=${NPM_AUTH_TOKEN}Being logged in to the private registry before running Kodine ensures packages resolve from your enterprise registry.