Build and test every tagged release
Connect
SPIRITT
NamespaceNamespace Devboxes
Real machines on demand
SPIRITT spins up Namespace Devboxes for work that needs dedicated hardware, from Apple Silicon Macs with Xcode to Linux machines with Docker. It runs builds, tests and long jobs there, brings back the results and expires every machine it creates.
What you can do with Namespace.
macOS without owning Macs
Run Xcode builds and macOS-only tooling on Apple Silicon Devboxes that nobody on your team has to maintain.
A clean machine every run
Ephemeral Devboxes start from a known image for each task and are expired afterward, even when the run fails.
Capacity reused, not wasted
SPIRITT reuses suitable running Devboxes and releases pool leases as soon as work finishes, so machines don't sit idle.
Works with your other apps.
Get started in three steps.
01
Open your workspace
Start a SPIRITT workspace for the builds, tests and jobs that need their own machines.
02
Connect Namespace
Sign in to your Namespace account once from your workspace. The approved login is kept in the workspace and reused for every task.
03
Delegate an outcome
Ask SPIRITT to build, test or run a job on a Devbox. It returns the results and cleans up the machine.
Hand over a mission.
Choose a mission. Make it yours.
Put Namespace to work.
Real hardware, zero upkeep
Questions
Namespace, with SPIRITT.
01What are Namespace Devboxes?+
Managed Linux and macOS machines in the cloud. Linux Devboxes run from a container image and include Docker; macOS Devboxes run on Apple Silicon with a choice of macOS and Xcode versions. SPIRITT creates them for a task, runs commands there and returns the results.
02How do I connect my Namespace account?+
SPIRITT supports Namespace natively. Open the sign-in link SPIRITT gives you and approve it once; the login stays in your workspace and SPIRITT never asks for or handles your credentials.
03Who cleans up the machines?+
SPIRITT does. Devboxes it creates are expired when the work finishes, including after a failure, and every pool lease it acquires is released.
04Can it reuse capacity I already have?+
Yes. SPIRITT checks your running Devboxes and reuses a suitable one, or acquires a machine from a pool and releases the lease when the run is done.
05Where do code changes end up?+
In source control. SPIRITT treats Devboxes as workers and keeps durable changes in your GitHub or GitLab repositories as commits, pull requests and merge requests.
06When is a Devbox the right choice?+
When a task needs macOS, Xcode, a larger machine or a long run that shouldn't depend on a laptop. Everything else runs directly in your SPIRITT workspace.