Sign in
INTRODUCING DOCKOCK Infrastructure, on your terms

Your infrastructure.
Beautifully under control.

Deploy applications. Connect your servers. See how it all fits together.
VPS management and application deployment, in one workspace.

Bring your own VPS Review before you deploy
dockock / your connected workspaceProduct vision
INFRASTRUCTURE → APPLICATIONS → OPERATIONS

Your entire project. Connected.

Start with your servers. Bring every service into the same picture.

Workspace infrastructure
FROM SOURCE

GitHub

Connect a repository and branch to build your application.

OR
ALREADY RUNNING

Self-deployed

Connect an existing deployment and map its services.

04 / RUN WITH DOCKER

One application. Purpose-built containers.

Review your deployment, then run services on your selected VPS or cluster.

ContainersPrivate networksPersistent volumes
Illustrative workflow. Cluster orchestration, automated DNS, full source builds and email lifecycle are in development. See what’s available
FAMILIAR FOUNDATIONSYour stack. Connected.See capability status
YOUR WORK. YOUR DOMAIN.

3 free business email addresses.
Your name. Your domain.

Create a professional identity with work email addresses on your own domain. Bring your CEO, team and support inboxes together with DOCKOCK.

Your domain. Every device.3 business email addresses · free
$0
Your mail serveryourcompany.comEmail deliveryceo@yourcompany.comteam@yourcompany.comsupport@yourcompany.com
Your professional identity, wherever you work.
01 / YOUR WORKSPACE

Your entire infrastructure.
Connected in DOCKOCK.

Manage multiple servers, applications, Kubernetes clusters and business email on your own domains—with security controls in the same workspace.

01

Manage every server in one place

Bring VPS instances from your hosting providers into one workspace. Keep track of your servers and the applications running on them.

02

Put your domains to work

Connect your domains to applications and create branded email addresses for your team. Keep projects, databases and inboxes organized together.

03

Grow with control

Run workloads across Kubernetes clusters as your needs grow. Control access, protect credentials and review changes across your infrastructure.

See how DOCKOCK works
DOCKOCK WORKSPACEInfrastructure & services
Multiple serversAcross your hosting providers.
Kubernetes clustersWorkloads across connected servers.
Security controlsAccess, credentials and reviewed changes.
Applications & domainsProjects linked to their web addresses.
Email on your domainBusiness inboxes with your own identity.
Explore the DOCKOCK platform

Your infrastructure. Your ownership.

VPS purchasing Planned add-on
02 / DEPLOY

From source to service.
With clarity at every step.

Run websites, APIs, and databases on your selected VPS. Understand the architecture and review the deployment before it changes your infrastructure.

EXAMPLE STACK

This web, API and database stack shows how services connect. Your project may use different frameworks, databases or service combinations, with deployment settings suited to its supported workloads.

Select a service to inspect its configuration
compose.yaml Example stackDownload YAML
# Application deployment example. Supply reviewed application images first.# Web contract: HTTP on port 3000. API contract: Node.js, HTTP on port 8080,# GET /health, and support for DB_PASSWORD_FILE. Public routing is configured# separately in DOCKOCK. Pin image digests before a production deployment.name: application-stack services:  web:    image: ${WEB_IMAGE:?Set a reviewed web image}    init: true    restart: unless-stopped    read_only: true    tmpfs: [/tmp]    cap_drop: [ALL]    security_opt: [no-new-privileges:true]    expose: ["3000"]    networks: [edge, application]    depends_on:      api:        condition: service_healthy   api:    image: ${API_IMAGE:?Set a reviewed Node.js API image}    init: true    restart: unless-stopped    read_only: true    tmpfs: [/tmp]    cap_drop: [ALL]    security_opt: [no-new-privileges:true]    expose: ["8080"]    networks: [application, data]    environment:      DB_HOST: database      DB_NAME: application      DB_USER: application      DB_PASSWORD_FILE: /run/secrets/db_password    secrets: [db_password]    depends_on:      database:        condition: service_healthy    healthcheck:      test: ["CMD", "node", "-e", "fetch('http://localhost:8080/health').then(r => process.exit(r.ok ? 0 : 1)).catch(() => process.exit(1))"]      interval: 15s      timeout: 5s      retries: 3      start_period: 20s   database:    image: postgres:16-alpine    restart: unless-stopped    networks: [data]    environment:      POSTGRES_DB: application      POSTGRES_USER: application      POSTGRES_PASSWORD_FILE: /run/secrets/db_password    secrets: [db_password]    volumes:      - postgres_data:/var/lib/postgresql/data    healthcheck:      test: ["CMD-SHELL", "pg_isready -U $$POSTGRES_USER -d $$POSTGRES_DB"]      interval: 10s      timeout: 5s      retries: 5      start_period: 20s networks:  edge: {}  application: {}  data:    internal: true volumes:  postgres_data: {} secrets:  db_password:    file: ./secrets/db_password
Web applicationLines 8–21Backend APILines 22–47DatabaseLines 48–65
DEPLOYMENT REVIEW / 01
Web application
SERVICE ROLE

Your frontend. Your framework.

Give your website or frontend a place in the stack. Its runtime, routes and service connections depend on how your application is built.

Web application
Backend services
CONFIGURED FOR YOUR PROJECT
Runtime
Your supported application image
Routing
The ports and domains your app needs
Dependencies
The services your frontend connects to

In this exampleThis YAML uses port 3000 and waits for the API health check.

Explore deployment workflow
DEPLOYMENT REVIEW / 02
Backend API
SERVICE ROLE

Your backend. Your business logic.

Connect the services behind your application. Configure each supported backend around its own runtime, dependencies and access requirements.

Backend service
Data services
CONFIGURED FOR YOUR PROJECT
Runtime
Your supported backend image
Health checks
A check suited to your service
Connections
Private services and required credentials

In this exampleThis YAML uses port 8080, a /health endpoint and a database secret.

Explore deployment workflow
DEPLOYMENT REVIEW / 03
Database
SERVICE ROLE

Your data. Your database choice.

Use a supported database that fits your application. Storage, credentials and network access should follow the needs of that database engine.

Database service
Persistent storage
CONFIGURED FOR YOUR PROJECT
Database engine
Your choice from supported workloads
Storage
Persistent storage for your data
Access
Connections limited to the services that need them

In this examplePostgreSQL 16 is used in this YAML example. Other engines need their own configuration.

Explore deployment workflow
Deployment availability

Compose foundations are in place. Public builds and the full GitHub workflow are in development.

View roadmap
03 / CONNECT YOUR SERVICES

Your domains. Every connection.
Give your services a home.

Bring your websites, application routes and business email together under your own domains. Follow each address back to the service behind it.

Domain automation · planned

From a domain name
to connected services.

A guided path from your registrar to your applications and email, with DNS settings in one workspace.

  1. 01
    Bring your domainAdd the domain you already own.
  2. 02
    Connect its DNSUpdate nameservers at your registrar, then verify.
  3. 03
    Choose where it leadsLink web addresses and mail records to your services.
Explore domain management
DOMAIN CONNECTIONSWorkflow preview
YOUR DOMAIN IN DOCKOCKyourcompany.com
Websitewww.yourcompany.com
A / CNAMEWeb application
Application APIapi.yourcompany.com
A / CNAMEAPI service
Business email[email protected]
MXMail service
YOUR NAME. YOUR BUSINESS.

A familiar name in every inbox.

Business email on your domain, with mailbox and DNS setup in the same workspace.

ceo@yourcompany.comteam@yourcompany.comcontact@yourcompany.comPlanned email workflow
Explore email
04 / SCALE WITH INTENTION

More servers.
One coordinated system.

Start with a single VPS. The planned Kubernetes workflow brings eligible servers together for distributed application workloads.

Give each service its own role.Web applications, APIs, and background workers.
Plan how infrastructure works together.Node roles, private networks, traffic, and storage.
Kubernetes workloadsOn the roadmap
Explore clusters & microservices
Compare infrastructure topologies
INFRASTRUCTURE TOPOLOGY
Application traffic
Routing & load balancingDirect requests to application services
VPS 01Web · API
VPS 02Web · API
VPS 03API · Worker
05 / STAY IN CONTROL

Confidence comes
from knowing what changes.

From server access to deployment approval, keep authority connected to the person responsible for the infrastructure.

Explore access & security
Explore ownership, access, and approval
OwnershipAccessApproval

Your infrastructure stays yours.

Keep your provider account and server ownership. DOCKOCK organizes your infrastructure within your workspace.

Workspace ownershipConnected infrastructure

Access with a clear purpose.

Verify server identity and authorize the connection. Review the access needed for the supported operation.

Identity verificationAuthorized server access

You decide when change happens.

Inspect the target, services, and proposed operation. Your approval applies to the reviewed plan.

Reviewable plansExplicit approval
A WORKSPACE THAT GROWS WITH YOU

Pay for the control plane.
Keep your infrastructure choices.

Choose a workspace around the servers and projects you manage. Provider bills and optional services remain separate.

Workspace plans

Hobby, Pro or Scale. Choose the capacity that fits your infrastructure.

Access details
Choose your billing period

Hobby

For individual developers and personal projects.

$12/ month · USD

Billed monthly per workspace.

  • Connected VPS2
  • Projects10
Explore Hobby
Included in Hobby
  • Guided server connection
  • Docker resource management
  • Reviewed deployment planning
  • Standard support

Scale

For agencies and larger application workloads.

$55/ month · USD

Billed monthly per workspace.

  • Connected VPS10
  • Projects150
Explore Scale
Included in Scale
  • Everything in Pro
  • Expanded server and project capacity
  • One workspace for larger workloads
  • Standard support

One project includes its frontend, API, database and workers. All prices are per workspace in USD; applicable taxes are additional.

Services around your stack.

Infrastructure costs remain separate from your workspace.

VPS purchasingProvider & pricing to be confirmedPlannedSelf-hosted emailIncluded in Pro & Scale when releasedPlanned
BEFORE YOU GET STARTED

Good questions.
Clear answers.

Understand the platform,
the plans, and the path ahead.

Read all FAQs
01What does DOCKOCK manage?

DOCKOCK connects VPS infrastructure and Docker resources in one workspace, with foundations for reviewed deployment operations. Automated domains, full email lifecycle management, and Kubernetes workloads are on the roadmap.

02Do I keep ownership of my server?

Yes. With the bring-your-own VPS path, your server stays in your provider account. You authorize the connection and review supported infrastructure changes in DOCKOCK.

03How will domain configuration work?

The planned workflow lets you add a domain and delegate its nameservers to DOCKOCK. After verification, DOCKOCK will configure supported DNS records, routing, and HTTPS. Authoritative DNS is not yet available.

04Can I combine multiple VPS instances?

Multiple VPS management and Kubernetes orchestration are different capabilities. The planned Kubernetes workflow will connect eligible servers into a cluster with defined networking, node roles, and storage. Customer Kubernetes workload deployment is not yet available.

05What is included in the subscription?

Hobby, Pro and Scale cover your DOCKOCK workspace and their listed server and project allowances. One application and its services count as one project. VPS provider bills, domain registration and optional services are separate. Need more capacity? Contact sales.

06Can I buy a VPS through DOCKOCK?

VPS purchasing is a planned add-on. The provider has not been confirmed and purchasing is not yet available. You can follow the bring-your-own VPS path as the foundation of the platform.

YOUR NEXT PROJECT STARTS WITH A BETTER FOUNDATION

Build what comes next.
Know what’s underneath.

Discover a clearer way to manage your own infrastructure.