Orbit
Search ⌘K
Documentation

Services

Run shared engines beside the projects that use them.

Manage local services and language runtimes from Orbit instead of scattering setup across terminals.

Shared engines

Services are downloaded and started on demand.

Orbit manages Mailpit, PostgreSQL, MinIO, and Redis-compatible storage. Service rows expose status, setup values, start and stop actions, and uninstall actions.

  1. Open Services to inspect engine state.
  2. Start an engine manually when you want it available before a project runs.
  3. Use setup values when an app needs connection strings or ports.
  4. Uninstall only when the binary and captured service data should be removed.
Orbit Services screen
Services shows engine status, setup values, and lifecycle actions together.

Use this screen to start engines before a project needs them, copy setup values, or remove data when the local service state is stale.

Project services

Project service selection stays scoped.

The project Services tab controls which engines belong to the selected project. When a project starts, Orbit starts enabled engines, provisions per-project resources, and injects missing environment values.

  • PostgreSQL creates one database per project slug.
  • MinIO creates one bucket per project slug.
  • Redis-compatible storage uses a per-project data file.
  • Service environment values are injected only when the project has not already set that variable.
Orbit project Services tab
The project Services tab keeps enabled engines scoped to the selected app.

Use the project tab to keep dependencies scoped. Orbit can provision project databases, buckets, and injected variables from this selection.

Language runtimes

Runtime versions can be bundled or system-managed.

Runtimes covers Node.js, PHP, and Python. Orbit detects system runtimes, can install managed versions, and resolves project runtime needs from files such as .nvmrc, .node-version, composer.json, .python-version, and pyproject.toml.

  1. Open Runtimes to inspect installed managed versions.
  2. Install a version before a project needs it when network access is limited.
  3. Enable prefer system runtime when the machine runtime should win.
  4. Remove unused managed versions after confirming no project needs them.
Orbit Runtimes screen
Runtimes shows managed and system versions before a project starts.

Use Runtimes before blaming project code for command failures. Version selection often explains install, build, and start errors.