Packaging for teams running services on their own or client infrastructure

Loading account state...

Back

Business paths

Trial stays the public evaluation entry point. This page is for the next step: internal team use, agency delivery, or custom commercial rights.

Internal Team

Paid workspace

For teams running Docker services on company-owned VPS, dedicated servers, or private cloud.

  • Path from evaluation to paid access
  • Guided onboarding on self-owned infrastructure
  • Deployment passport for readable runtime review
  • Commercial use covered explicitly
Primary wedge

Agency / Multi-client

Commercial package

For agencies, integrators, and outsourced teams supporting services on client-owned infrastructure.

  • Client infrastructure support path
  • Packaging shaped around ongoing support and handoff
  • Reusable handoff assets for repeat client delivery
  • Conversation starts from delivery model, not from generic seat count

Custom / Redistribution

Separate agreement

For managed service, SaaS embedding, redistribution, resale, or white-label style use.

  • Redistribution and resale review
  • Support and customization discussion
  • Rights review anchored to the live product path
  • Explicit commercial licensing path

How the path works

The public product stays open for evaluation. Business use, internal company use, client work, SaaS use, resale, and redistribution still require an explicit paid or commercial agreement.

Read policyCommercial license page
Stay on the public path when
You are still evaluating the workflowYou want to see whether the product fits your infrastructure modelYou are not yet using the code for business or client operations
Move into a paid or commercial path when
Internal company deployment operationsAgency or client delivery on customer infrastructureCommercial SaaS or managed serviceRedistribution, white-label, or resale
What is already real in the product
Deployment passport keeps runtime identity, health proof, recent activity, and the next safe action in one blockTemplates now read as reusable handoff assets for repeat services, clients, or operator swapsThe public business path already separates evaluation, internal-team use, agency delivery, and custom licensing
Russian operator materials
Russian install quickstart: Self-hosted setup on one VPS or dedicated host: env, known_hosts, compose up, and first live checks.Russian operator quickstart: First operator path from server review to deployment passport and handoff in plain Russian.Russian pilot onboarding checklist: First-week commercial path: scope review, install, first deploy, handoff check, and support rhythm.Russian design-partner demo packet: The 10-15 minute buyer path: public story, live product, deployment passport, handoff proof, and next pilot step.
Pilot onboarding and support motion
Short scope review before the pilot becomes active deliveryOne concrete self-hosted install pathOne first deploy plus deployment-passport handoff checkOne explicit week-one support rhythm around review, health, and ownership

Start the access conversation

Use this form after evaluation when you want the right business path for your internal team, agency workflow, or custom commercial use.