Pricing · Licensing

Open source to run. Licensed for private delivery.

The OpenViking core is fully open source, self-hostable, and free forever. When you want the private-delivery Enterprise edition — manageable licensing, longer leases, and operational support — it is licensed through Volcengine. In every edition your agents' context data stays inside your own environment.

No credit card for the trial · context data never leaves your environment

Two ways to deliver

One core, two ways to deliver it

Open source

Community

Freeopen source · self-host

The full open-source core. Clone it, build it, run it on your own infrastructure — no key, no activation.

  • Complete open-source core (ov)
  • Self-hosted in your own environment
  • Context data stays 100% local
  • No license, no online activation, no telemetry
  • Community support: GitHub issues & discussions

License: open source

Private delivery

Enterprise

Per seat / yearvia Volcengine · contact us

The open-source core plus a private-delivery build, manageable licensing, and operational support.

  • Everything in Community
  • Private-delivery build for your environment
  • License key + online activation
  • Signed lease (~7 days) with automatic refresh
  • Revoke / resume controls
  • Operational telemetry (per-org preference) & management console (later milestone)
  • Priority support with an SLA

Purchased via Volcengine

How licensing works

Licensing, in one paragraph

A license key lets your private deployment activate online and receive a short-lived signed lease, which it keeps refreshing. Revoke and resume take effect at the next refresh. There is no offline mode — the short lease itself is the grace window that tolerates brief refresh blips.

  1. Get a key

    Issue a license key by email (free for a trial, or Enterprise via Volcengine). The key is an opaque string, like ovk_trial_… / ovk_ent_….

  2. Activate online

    Your deployment presents the key; the official API validates its status and expiry and returns a short-lived signed lease (ES256, ~7 days) plus a signed key manifest to verify against.

  3. Refresh & run

    The deployment verifies the lease signature locally, runs, and refreshes the lease before it expires. The short lease is the grace window for brief refresh interruptions.

  4. Revoke / resume

    Status changes take effect at the next refresh: revoke → refresh returns 403 and the deployment stops serving once its current lease lapses; resume → refresh succeeds again.

Once you have a key, activate it in your own private environment (the mock private deployment):

$ go run ./cmd/ovd run --key <key>

Only the key refresh and (optional) operational telemetry ever leave — your context data stays in your environment.

Data boundary

What stays, what leaves

Agent context is sensitive data, so it stays inside your own environment. Only minimal operational information ever leaves.

Stays in your environment

  • Agent context data and files
  • Your customer content and business data
  • The deployment's private key (P-256, customer-held; the control plane stores only the public key and thumbprint)

Leaves (minimal · operational only)

  • The license key presented at activation and refresh
  • Short-lived lease requests (no content payload)
  • Optional operational telemetry: heartbeat, version, counters — gated by your org preference, never a billing source

FAQ

Questions about licensing

Is Community really free?

Yes. The core is fully open source and self-hostable with no key, no online activation, and no telemetry.

What happens if a refresh fails?

The current signed lease (~7 days) keeps the deployment running as a grace window; it only stops serving if the lease lapses without a successful refresh.

Can we revoke a deployment?

Yes. Revoke / resume from the control side; the effect applies at the deployment's next refresh (bounded by the lease TTL).

Does our data go to your cloud?

No. Context data stays in your environment; only the key refresh and optional operational telemetry leave.

How do we buy Enterprise?

Through Volcengine. You receive an Enterprise key, then use it to activate your own private deployment.

Start private, stay private.

Run it in your own environment with a free trial key; when you are ready for private delivery, upgrade to Enterprise via Volcengine.