You can now understand how your Namespace Compute usage is spread accross our various products.

You can now install our CLI with brew install namespacelabs/namespace/nsc.

Provide Namespace with a custom base image to install additional tools or dependencies to run your Buildkite pipelines.

Leverage our local, high-performance Cache Volumes to vastly speed up your CI runs.

Significantly speed up your GitHub Action runs through Cache Volumes. Skip fetches from remote caches - your files are already available locally.

Cache volumes run on local, high-performance storage allowing them to vastly outperform remote caching solutions.

Shape your Buildkite Agents perfectly to your needs by selecting vCPU count, RAM size and architecture.

Namespace can automatically generate previews for your Kubernetes applications. Namespace’s ingress manager observes annotations on your services to expose previews automatically.

Quick access to all ingresses exposed by your application.

Instead of C.UTF-8, you can now switch your GitHub runners to use POSIX.

You can now inspect your AWS Cognito federation configuration under Federation in the Dashboard.

Every docker build handled by Namespace's remote builders now gets its own trace view. You can now more intuitively debug why a particular build didn't perform as you expected.

You can now call Namespace from your Circle CI workflows. For example, speed up your builds by relying on Namespace' Remote builders.

By default, Remote Builders now have 64GB of high-performance disk storage available for caching.

Labels are rendered in the Dashboard, and can be used to distinguish instances ("clusters") that have different purposes.

Check the different in spend based on number of minutes you spend in GitHub Actions.

In addition to compute unit minutes, builds are also available now under usage.

Wondering if an arm64 builder is up and running as well? The summary page now shows all active builders per workspace.

We've updated the maximum instance size from 16 vCPU to 32 vCPU for all your large parallel computation needs.

You can now seamlessly use your AWS resources from Namespace instances, and also create and manage Namespace resources from your AWS resources, by relying on Workload Identity Federation.

Each instance you run concurrently, for example, by using GitHub Actions Runners, uses your concurrency limits. When these are hit, new instance are queued and not created immediately. Previously you'd have to monitor usage via the dashboard. But now you get notifications to your inbox when limits are hit. These notifications can be disabled as well.

Useful when interacting with Namespace programatically, and you need to quickly check what is the id of your workspace.

Errors of containers that fail are now surfaced automatically in the Dashboard, for quick debugging.