Enterprise
Using InnoCode securely in your organization.
InnoCode Enterprise is for organizations that want to ensure that their code and data never leaves their infrastructure. It can do this by using a centralized config that integrates with your SSO and internal AI gateway.
To get started with InnoCode Enterprise:
- Do a trial internally with your team.
- Contact us to discuss pricing and implementation options.
Trial
InnoCode is open source and does not store any of your code or context data, so your developers can simply get started and carry out a trial.
Data handling
InnoCode does not store your code or context data. All processing happens locally or through direct API calls to your AI provider.
This means that as long as you are using a provider you trust, or an internal AI gateway, you can use InnoCode securely.
Code ownership
You own all code produced by InnoCode. There are no licensing restrictions or ownership claims.
Pricing
We use a per-seat model for InnoCode Enterprise. If you have your own LLM gateway, we do not charge for tokens used. For further details about pricing and implementation options, contact us.
Deployment
Once you have completed your trial and you are ready to use InnoCode at your organization, you can contact us to discuss pricing and implementation options.
Central Config
We can set up InnoCode to use a single central config for your entire organization.
This centralized config can integrate with your SSO provider and ensures all users access only your internal AI gateway.
SSO integration
Through the central config, InnoCode can integrate with your organization’s SSO provider for authentication.
This allows InnoCode to obtain credentials for your internal AI gateway through your existing identity management system.
Internal AI gateway
With the central config, InnoCode can also be configured to use only your internal AI gateway.
You can also disable all other AI providers, ensuring all requests go through your organization’s approved infrastructure.
Self-hosting
While we recommend disabling the share pages to ensure your data never leaves your organization, we can also help you self-host them on your infrastructure.
This is currently on our roadmap. If you’re interested, let us know.
FAQ
What is InnoCode Enterprise?
InnoCode Enterprise is for organizations that want to ensure that their code and data never leaves their infrastructure. It can do this by using a centralized config that integrates with your SSO and internal AI gateway.
How do I get started with InnoCode Enterprise?
Simply start with an internal trial with your team. InnoCode by default does not store your code or context data, making it easy to get started.
Then contact us to discuss pricing and implementation options.
How does enterprise pricing work?
We offer per-seat enterprise pricing. If you have your own LLM gateway, we do not charge for tokens used. For further details, contact us for a custom quote based on your organization’s needs.
Is my data secure with InnoCode Enterprise?
Yes. InnoCode does not store your code or context data. All processing happens locally or through direct API calls to your AI provider. With central config and SSO integration, your data remains secure within your organization’s infrastructure.
Can we use our own private NPM registry?
InnoCode supports private npm registries through Bun’s native .npmrc file support. If your organization uses a private registry, such as JFrog Artifactory, Nexus, or similar, ensure developers are authenticated before running InnoCode.
To set up authentication with your private registry:
npm login --registry=https://your-company.jfrog.io/api/npm/npm-virtual/This creates ~/.npmrc with authentication details. InnoCode will automatically
pick this up.
Alternatively, you can manually configure a .npmrc file:
registry=https://your-company.jfrog.io/api/npm/npm-virtual///your-company.jfrog.io/api/npm/npm-virtual/:_authToken=${NPM_AUTH_TOKEN}Developers must be logged into the private registry before running InnoCode to ensure packages can be installed from your enterprise registry.