Enterprise

Using Fring securely in your organization.

Fring 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 Fring Enterprise:

Do a trial internally with your team.
Contact us to discuss pricing and implementation options.

Trial

Fring does not store any of your code or context data, so your developers can simply get started and carry out a trial.

Data handling

Fring does not store your code or context data. Model requests are routed through the Fring Zen gateway, which is how usage is metered; organizations that need traffic to stay on their own infrastructure can point Fring at an internal AI gateway instead, with every other provider disabled.

This means that as long as you are using a provider you trust, or an internal AI gateway, you can use Fring securely.

Code ownership

You own all code produced by Fring. There are no licensing restrictions or ownership claims.

Pricing

Enterprise workspaces are licensed per seat, with a token allowance pooled across the whole workspace rather than divided per user — so one developer’s heavy week is not blocked while a colleague’s allowance goes unused. Five-seat minimum. For pricing and implementation options, contact us.

Deployment

Once you have completed your trial and you are ready to use Fring at your organization, you can contact us to discuss pricing and implementation options.

Central Config

We can set up Fring 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, Fring can integrate with your organization’s SSO provider for authentication.

This allows Fring to obtain credentials for your internal AI gateway through your existing identity management system.

Internal AI gateway

With the central config, Fring 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.

FAQ

What is Fring Enterprise?

How do I get started with Fring Enterprise?

Simply start with an internal trial with your team. Fring 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?

Per seat, with a token allowance pooled across the workspace rather than divided per user. Five-seat minimum. Contact us for a quote.

Is my data secure with Fring Enterprise?

Model requests are routed through the Fring Zen gateway, which is how usage is metered. Organizations that need traffic to stay on their own infrastructure can be configured against an internal AI gateway instead, with every other provider disabled. For current data-handling, retention and residency terms, contact us — they depend on the provider behind each model.

Can we use our own private NPM registry?

Fring 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 Fring.

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. Fring 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 Fring to ensure packages can be installed from your enterprise registry.