Business path

Choose the right path for internal teams, agency delivery, or commercial redistribution.

DeployMate stays open for public evaluation, but business use of the code still requires an explicit paid or commercial agreement. This page explains the buyer-facing paths before you start that conversation.

Evaluation stays self-serve

The live app and trial path stay available when you are still deciding whether the workflow fits your team or clients.

Business use stays explicit

Internal company operations, client delivery, SaaS embedding, resale, and redistribution are handled through a paid or commercial path.

The buyer path should feel clearer

We frame the conversation around infrastructure type, support model, runtime handoff needs, and rights needed instead of sending everyone through the same vague review wording.

Business use

Pick the path that matches how you support services

Use the public product to evaluate. Use one of the paths below when DeployMate becomes part of real business operations.

Buyer-facing path
Business paths
Internal Team: For teams deploying Docker services on company-owned infrastructure and moving from evaluation to explicit business use.Agency / Multi-client: For agencies, integrators, and outsourced teams supporting services on client-owned infrastructure.Custom / Redistribution: For SaaS embedding, managed service, resale, redistribution, or white-label use.
What to include in the request
Company or project nameWhether the infrastructure is company-owned, client-owned, or mixedExpected number of services, servers, or environmentsWhat runtime handoff or multi-operator workflow you needWhether you need support, customization, or redistribution rights
What product proof already exists
Deployment passport already keeps runtime identity, health proof, recent activity, and the next safe action togetherTemplates already work as reusable handoff assets for repeat services or client environmentsThe 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 the first live checks.Russian operator quickstart: The first operator path from server review to deployment passport and handoff without SSH folklore.Russian pilot onboarding checklist: The first-week commercial path: scope review, install, first deploy, handoff check, and support rhythm.Russian design-partner demo packet: The buyer demo path: public story, live product, deployment passport, handoff proof, and next pilot step.
Pilot onboarding and support motion
Short scope review before any agreement is treated as active deliveryOne self-hosted install path instead of vague setup promisesOne first deploy plus deployment-passport handoff checkOne explicit week-one support rhythm for review, health, and ownership
Running services for your own company?

Use the upgrade path to move from evaluation into an explicit Internal Team agreement instead of keeping business use implicit.

Supporting client infrastructure?

The first wedge is the agency and integrator path: describe your delivery model, number of services, and what handoff or reusable-asset shape you need.

What happens next?

After you submit the request, the next step is a short scope review: infrastructure type, deployment scale, support needs, and whether redistribution rights are required. The first reply usually comes within 2 business days.

What to prepare

Have your company/project name, infrastructure model, estimated footprint, runtime handoff needs, and any support or customization requirements ready before the conversation.

Need Russian-first proof before the call?

Start with the Russian install quickstart for the first self-hosted setup path, then use the operator quickstart, pilot onboarding checklist, and design-partner demo packet to review the first deploy, handoff, support rhythm, and live buyer conversation in plain language.

Why this matters for the buyer

The commercial path is easier to justify when the team can already see real install, operator, pilot-support, and demo materials for the same client-infra workflow the product is selling.

Start business path conversationEmail business use requestRead full policyOpen live product
Back to homepageEvaluation stays easy. Business use stays explicit.