PLATFORM / DEPLOYMENTS

From application source.
To a reviewed deployment.

Bring a GitHub project or an existing self-deployed application into the intended workflow. Define its services, map domain routes, and review the target before deployment.

Explore the workflow Full product tour

Compose foundations

Project deployment planProduct concept

DOCKOCK / DEPLOYMENTSYour connected workspace

GitHub source / existing deploymentPlanned

WebAPIData

The public applicationRoute your root domain to the service people visit.

Route: dockock.example
Service: Web · port 3000
Dependency: Private API

Your application logicGive the API a deliberate public or private boundary.

Route: api.dockock.example
Service: API · port 8080
Dependency: Private database

A persistent foundationKeep database access internal and preserve data between releases.

Route: Internal network only
Service: PostgreSQL · port 5432
Storage: Persistent volume

THE WORKFLOW

A clear path.
At every stage.

Follow the intended workflow, with availability explained above.

Add the project

Connect source or describe an existing deployment in the planned onboarding flow.

Define service routes

Map domains and subdomains to the web, API, and microservices that need them.

Approve the exact plan

Review capacity, dependencies, health checks, and persistent data before a supported deployment.

DESIGNED AROUND THE DETAILS

The context behind the controls.

Explore the decisions, operating responsibilities, and current implementation behind this part of DOCKOCK.

Explore the guides

Understand what the source needs.

Source ZIP analysis identifies supported application patterns and proposes services, ports, dependencies and persistent storage. A detected framework helps with planning; it does not guarantee a successful build.

Review detected services and warnings
Confirm build and start commands
Identify database and storage requirements

Review the complete change.

Deployment approval is tied to a specific plan fingerprint. Supported Compose workflows describe service dependencies, health checks, networks and storage from the reviewed plan.

Capacity preflight
Explicit plan approval
Deployment progress and event context

Build availability is limited.

Public builds are disabled. A complete customer workflow from GitHub connection through building and deployment is still in development. Review current availability before choosing DOCKOCK for continuous deployment.

From application source.
To a reviewed deployment.

A clear path.
At every stage.

Add the project

Define service routes

Approve the exact plan

The context behind the controls.

Understand what the source needs.

Review the complete change.

Build availability is limited.

DOCKOCK support

A little help.
A clearer next step.

From application source.To a reviewed deployment.

A clear path.At every stage.

Add the project

Define service routes

Approve the exact plan

The context behind the controls.

Understand what the source needs.

Review the complete change.

Build availability is limited.

Connect the next layer.

See the whole workflow.Know where to begin.

From application source.
To a reviewed deployment.

A clear path.
At every stage.

See the whole workflow.
Know where to begin.