One governed product. Three operating boundaries.

Use DEP in VerShep Cloud, on one customer-controlled machine as a Local Farm, or inside qualified private infrastructure. The accepted-outcome model stays consistent; identity, backup, updates, support, and provider connectivity reflect the boundary you choose.

Available in Public Early Access

VerShep Cloud

Best fit: The fastest self-serve start with no installation to manage.

VerShep operates the application and managed product storage.

Open DEP from a supported browser
Start with Free or subscribe to Founding Pro
Receive product updates through the managed service
Export Change Passports and supported account data

Start free in DEP

Qualification-first private evaluation

Local Farm

Best fit: A customer-controlled machine when local custody and operational control matter most.

The customer operates a signed VerShep runtime and stores DEP tenant data on that machine.

Prebuilt proprietary runtime, not a CPF or DEP source-code handoff
Customer-readable configuration, evidence, exports, and backup procedures
Telemetry disabled by default and updates applied deliberately
Explicit configuration for every model provider and external connector

Request deployment qualification

Qualification-first private evaluation

Private Farm

Best fit: A customer VPS, private cloud, or supported K3s environment with organizational controls.

The customer or an approved operator manages the infrastructure inside a written deployment boundary.

Private network and identity integration scoped before installation
Persistent storage, backup, recovery, monitoring, and support requirements documented
Single-node evaluation profile available for qualification
High availability and regulated-environment claims require separate validation

Request deployment qualification

Local custody without hidden claims

Your Farm can stay on your machine.

A Local Farm is designed to keep DEP application data and its scheduler on a customer-controlled machine. VerShep protects its proprietary implementation through a signed prebuilt runtime; customer configuration, evidence, exports, and operational controls remain inspectable.

Local does not mean no network traffic under every configuration. If you enable a hosted model, Git provider, email service, payment service, or another connector, the explicitly scoped data needed for that service can leave the machine. Every connector must make that boundary visible before activation.

Current qualification boundary

Private packaging is real; general availability is not yet claimed.

DEP currently has a single-node container profile and a private K3s deployment foundation. Local Farm and Private Farm remain written-scope evaluation offers until supported-host testing, authentication, backup and recovery, update signing, monitoring, support, and security qualification are complete.

Pricing is quoted after qualification. Hardware, private infrastructure, customer model use, integrations, setup, and support remain separate unless a written offer includes them.

Review pricing boundaries Review security and trust