Cooker, with its letters forming a chef's hatFROM RECIPE
TO RUNTIME GitHub

THE SOFTWARE KITCHEN / OPEN SOURCE & SELF-HOSTED

A clear path.
From recipe
to runtime.

Good software needs more than a finished build. It needs the right steps, in the right order, with a clear place to go.

Cooker brings visual pipelines and reviewed Compose deployments into one workspace—on infrastructure you choose.

Explore a workflow Run Cooker locally ↗
Isometric charcoal kitchen: separate preparation stations connect through open aisles to plating and a doorway toward the dining destination. An ember floor route represents coordinated work.
An illustration of the workflow. Every station has a part to play.
YOUR SOURCEVISIBLE DEPENDENCIESDELIBERATE REVIEWYOUR INFRASTRUCTURE

01 / WHO WE ARE

Built for the people
behind the release.

Cooker is an open-source project from DravenIQ, made for developers and small teams who want to understand the work between a repository and a running application.

You bring the source and the infrastructure. Cooker gives the steps, dependencies, reviews and execution records a shared home.

Built in the open, on GitHub ↗
A cream recipe notebook on a charcoal kitchen desk, with a branching preparation sketch and carefully arranged components.
01 / THE RECIPE — make the plan visible.

WHY WE BUILD COOKER

A build is one step.
The whole recipe
matters.

A build command tells you one part of the story. Cooker is built around the rest: what depends on that step, what needs review, and where the result will run.

Like a well-run kitchen, the work should be easy to trace. Independent stations can work in parallel. A dependent step waits for its prerequisites. The final handoff has a destination.

Understand the pipeline ↗

02 / WATCH THE RECIPE TAKE SHAPE

Different stations.
One shared outcome.

Explore two example plans. Select a step to see what it does and why it waits. These examples explain the workflow; they do not run a deployment.

ILLUSTRATIVE / NOT A LIVE RUN
A reviewed release, with parallel checks.The image reaches Push only when both checks succeed.

PUSH / THE PLATING STATION

Wait for every required check.

Both test branches must succeed before the image is published to the registry.

Waits for: Unit tests + Smoke check

Read the pipeline guide ↗
Example plan. Selecting a step does not run work.Open the editable DAG example ↗

03 / THE PASS

Prepared with care.
Served with intention.

Saving a recipe and serving the result are different actions. Review the source and requirements, then deploy to your configured destination. Keep the attempt, its logs and its outcome in view.

Follow a reviewed Compose deployment ↗
The same charcoal kitchen's serving pass: a finished dish is checked under a warm lamp before its handoff to the table outside.
03 / SERVICE — a finished build still needs a destination.

04 / BRING YOUR INFRASTRUCTURE

One view.
Your choice of destination.

Run the supported parts of your Compose stack on a configured target. Keep an existing database where it already lives.

Docker Compose

Native stacks on the Cooker host, with service DNS and named volumes.

LOCAL HOST

Kubernetes

Deployments and Services on an existing, configured cluster.

EXISTING CLUSTER

ECS Fargate

A container service for each supported workload in your stack.

EXISTING AWS SETUP

Cloud Run

A supported single-container path on your configured GCP project.

EXISTING GCP SETUP

Current App flow: one compute target per stack. Target support depends on configuration and Compose compatibility. See the supported scope ↗

05 / YOUR WORKSPACE, ON YOUR MACHINE

Make room for
your next idea.

Start with a local look around. Bring your own infrastructure when you are ready to exercise real builds and deployments.

Read the quickstart
Requires Git, Docker, and Docker Compose.
Explore locally
git clone --branch develop \
  https://github.com/santapong/Cooker.git
cd Cooker
docker compose up --build
Then open http://localhost:8080
The default development stack explores the UI with authentication off and no-op execution backends. Use a trusted local environment; follow the UAT guide for real deployments.

BUILT IN THE OPEN

An honest look at where we are.

The reviewed GitHub Compose workflow is implemented on develop and ready for UAT. Human and live cloud acceptance are pending. Source builds currently use a dev/UAT-only Docker path; the compatible production build path is still ahead.

Read the current plan

06 / BEFORE YOU START

A few useful
answers.

Who is Cooker for?

Developers and small teams who want a self-hosted, visual way to understand and run container workflows. Cooker currently has instance-wide roles; it does not provide isolated customer tenants.

Does Cooker host my applications?

You host Cooker and configure the infrastructure where your workloads run. Cooker coordinates the supported deployment flow. It does not provision your cloud accounts, clusters, networks, or managed databases.

Can I use an existing database?

Yes. A reviewed Compose App can replace a database service with an external binding. Connection values come from a linked Environment. You provide connectivity, authentication, and TLS; verify database access from the deployed application.

What happens when my Git branch changes?

A reviewed Compose App stays pinned to its saved Git commit. Explicitly inspect the new revision and review it before updating. This reviewed workflow uses manual deployment.

Is Cooker open source?

Yes. Cooker is licensed under Apache 2.0. You can inspect the source, run it yourself, and contribute through the GitHub repository.

SEE WHAT YOU ARE SHIPPING.

Bring your next deploy
into the picture.

Get started with Cooker