Dropstone Docs

Enterprise

Using Dropstone securely in your organization.

Dropstone Enterprise is for organizations that want centralized config, SSO, and admin controls across their developers.

Note:

Dropstone does not store your code or context data. See Data handling below for the full posture.

To get started with Dropstone Enterprise:

  1. Run an internal trial with your team using the standard plan.
  2. Contact us to discuss pricing and implementation.

Trial

Your developers can install Dropstone today and start using it. See the Quickstart for the install flow. A trial does not require an enterprise contract, and nothing in the default configuration sends code to anyone outside the team.

Data handling

Your prompts, code, and conversation transcripts are never used to train models and are not retained beyond the lifetime of your session. Dropstone uses session-scoped prompt caching to reduce cost and latency, the same way Anthropic and OpenAI do: cached content is isolated to your own account, expires automatically, and is never reused for any other user or sent to model training.

These controls are enforced and reviewed by Blankline, Dropstone's parent company. Blankline's compliance team audits Dropstone's data handling on a recurring basis and retains revocation authority over the production access of any individual or system that breaches the policy.

See the Trust page for the full posture, including subprocessor disclosures and the runtime security boundary.

Code ownership

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

Pricing

Dropstone Enterprise uses a per-seat model with a flat monthly cost per developer. For details and a custom quote based on your organization's needs, contact us.

Deployment

Once you have completed your trial and are ready to roll Dropstone out across your organization, contact us to set up the enterprise contract and the central config.

Central config

Dropstone Enterprise organizations get a single central config that is served to every developer's CLI on sign-in. The config can pin:

  • Default model tier and reasoning effort
  • Permissions (which tools an agent can run without approval)
  • Allowed MCP servers
  • Audit and telemetry destinations

Users cannot override managed values locally. See Managed settings for the underlying mechanism (also available outside enterprise contracts for self-managed deployments).

SSO integration

Dropstone Enterprise integrates with SAML and OIDC identity providers (Okta, Azure AD, Google Workspace, and any standards-compliant IdP). Developers sign in through your existing identity system; revoking access in your IdP immediately revokes Dropstone access for that user.

FAQ

What is Dropstone Enterprise?

Dropstone Enterprise is a per-seat plan that adds SSO sign-in, a central config that admins control, an enterprise data-handling guarantee (no retention, no training, audited by Blankline), and a named point of contact for support.

How do I get started?

Run a trial internally first. Dropstone does not store your code or context data by default, so you don't need an enterprise contract to evaluate it. When you are ready to roll it out across the team, contact us.

How does enterprise pricing work?

Per-seat. For a custom quote based on team size and feature requirements, contact us.

Is my data secure with Dropstone Enterprise?

Yes. Dropstone does not retain your code, prompts, or conversation transcripts beyond the in-flight inference call, and never uses them to train models. Session-scoped prompt caching is isolated per account and expires automatically. These controls are reviewed by Blankline's compliance team on a recurring basis. See the Trust page for the full posture.

Can we use our own private NPM registry?

Yes. Dropstone supports private npm registries through standard .npmrc file support. If your organization uses a private registry (JFrog Artifactory, Nexus, GitHub Packages, or similar), authenticate developers before running Dropstone.

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. Dropstone picks it up automatically.

Note:

Developers must be logged into the private registry before running Dropstone, otherwise package installs from npm-based plugins will fail.

Alternatively, configure ~/.npmrc manually:

registry=https://your-company.jfrog.io/api/npm/npm-virtual/
//your-company.jfrog.io/api/npm/npm-virtual/:_authToken=${NPM_AUTH_TOKEN}
Ctrl+I