HYBRID EXECUTION
Native services and containers, together.
Run Spring Boot, Node, Go or Rust directly through their own toolchain while PostgreSQL, Redis and RabbitMQ stay containerized. Forge treats both as first-class resources.
forge · build · run · observe
Run your whole stack.
Locally.
Forge is a lightweight desktop control centre for local distributed development. Run native services and containers together, start only what you need, and see everything in one place.
Native processes Docker containers forge.yaml
Everything your stack needs, understood by Forge.
Applications
services · gateways · workers
Databases
postgres · mongo · mysql
Cache
redis · memcached
Messaging
rabbitmq · kafka · nats
Search
typesense · elasticsearch
Storage
minio · s3-compatible
Infrastructure
keycloak · mailpit
External
aws · stripe · twilio
Native processes and containers are first-class citizens — mix them freely.
THE WORKSPACE
One window.
Your entire local stack.
Stop juggling terminals. Forge shows what is running, what is broken, what depends on what, and where every byte of memory is going.
overview — Every resource, grouped by role, with a live dependency graph and workspace resource usage.
BUILT FOR REAL WORK
Developer experience,
without the overhead.
Forge does not try to be Kubernetes or Docker. It focuses on the one thing they do not: making your local environment simple to run and understand.
ORCHESTRATION
Dependencies come up in the right order.
Declare depends_on and Forge resolves the graph, starts what is missing, waits for readiness, and reports failures instead of leaving you guessing.
HEALTH
A focus on health that means something.
Distinguish "the process exists" from "the service is ready". HTTP, TCP and command checks drive clear, real-time states.
LOGS
One stream for everything.
Aggregate logs from native processes and containers, filter by resource or level, search, and jump from an error to its context.
OBSERVABILITY
Know your footprint.
CPU and memory per resource and for the whole workspace. Forecast before your laptop starts to sweat.
CONFIG AS CODE
A stack you can commit.
Describe the environment in a readable forge.yaml, share it through Git, and let anyone reproduce it with one command.
CLONE → OPEN → START → CODE
From clone to coding
in four steps.
A newly onboarded developer reproduces the whole environment with minimal manual setup.
- 01
Describe your stack
Write a forge.yaml — resources, ports, commands, images, dependencies and profiles. Commit it with your code.
workspace: name: my-project
- 02
Pick a profile
Minimal, Backend, Payments or Full. Start only the services you need right now, not the whole platform.
profiles: backend: [gateway, user-service]
- 03
Forge resolves the graph
Dependencies start first and are waited on for readiness. Failures propagate to dependents, clearly and immediately.
gateway → user-service → postgres
- 04
Ship features
Watch health, tail logs, read metrics, restart a single service. No local cluster, no wall of terminals.
environment ready in 14.8s
WHY FORGE
A third approach,
without the overhead.
Containers alone are heavy for application code; Kubernetes is overkill for a feature branch. Forge sits in between.
| Forge | Docker Compose | Local Kubernetes | Terminals & scripts | |
|---|---|---|---|---|
| Native processes and containers, together | ||||
| Dependency-aware startup with readiness | ||||
| Configuration committed to Git | ||||
| Per-resource health and logs in one place | ||||
| CPU and memory per resource | ||||
| No control plane, no cluster | ||||
| Lightweight control plane |
GET STARTED
Bring order to
your local stack.
Free, native, and built with Tauri. macOS · Windows · Linux.
View release feed
QUESTIONS
Good to know.
Everything you might ask before pointing Forge at a real project.
Is Forge a replacement for Docker or Kubernetes?
No. Forge is the developer-experience layer above your local processes and container runtime. It runs your application services as native processes and your infrastructure through Docker — it does not implement isolation itself or try to reproduce production orchestration.
Do I have to containerize my services?
Not at all. Native processes are first-class. Run ./gradlew bootRun, npm run dev, cargo run or go run while databases, caches and brokers stay in containers.
How is the environment shared with my team?
A readable forge.yaml committed to Git. It describes resources, ports, dependencies, health checks, profiles and actions, so anyone can reproduce the environment with minimal setup.
What does Forge need to run?
A native desktop app for macOS, Windows and Linux, built with Tauri and Rust. Containers require a local Docker-compatible runtime; everything else runs directly on your machine.
Will it slow my machine down?
Lightweight by design. The control plane stays minimal and there is no Kubernetes control plane. You start only the resources you need, per profile.
Your local development environment,
under control.
Open your repository, start a profile, and get to work.