Local application stacks
Start the database, API, queue, worker, repository service, relay, and helper processes an application needs.
Bus Services
Run the service stack your product depends on.
Bus Services gives any application one repeatable control surface for the long-running pieces around it: databases, APIs, worker runtimes, task queues, repositories, relays, background jobs, and provider-backed services.
Install the Bus binary tools
The standard BusDK installer installs the Bus binary tools used by Bus Services,
including the bus command and the Services modules included in the
release.
curl -fsSL https://install.busdk.com | bashOther downloads are available from github.com/busdk/busdk/releases.
Bus Services pricing
Start with the binary trial, continue with the binary subscription, choose the FSL source subscription when your team needs source that converts to MIT or Apache 2.0 two years after release, or buy a one-time MIT source release. Live prices and checkout are handled by the Stripe pricing table.
What it is
A service is something Bus can create, start, stop, observe, or verify. Bus
Services reads a public services.yml file, resolves the referenced
profiles, validates non-secret configuration, starts services in dependency order,
and records status under a Services state directory.
The same stack can be used by a developer on a laptop, by a CI smoke test, by a dedicated customer environment, or by a Docker image where Services supervises the application processes inside the runtime.
What it is for
Repeatable operations
Replace ad hoc setup notes with a stack file, a status command, log paths, and predictable shutdown behavior.
Deployment packaging
Copy a stack and profiles into an image or dedicated host and run one Services command as the process supervisor.
Supportable customer environments
Give operators a common way to inspect what is running without exposing secrets, DSNs, or private token values.
The everyday workflow
bus services stack validate
bus services stack plan
bus services up
bus services list
bus services down
Validation catches stack and profile errors before startup. Planning shows the
non-secret service plan. Startup freezes the resolved config so shutdown still
targets the running stack even if the source file changes later.
These commands use the normal defaults: services.yml, a
profiles/ directory when present, and .bus/services
state.
Where to go next
Getting started
Create a small stack, start it, inspect status, and stop it cleanly.
Examples
See a minimal native service and an existing repository stack shape.
Docker
Use Bus Services inside a runtime image without requiring PID 1.
Modules
Understand which modules own the CLI, API provider, integration runtime, and provider boundaries.