condensation Internal preview

Sandbox infrastructure for every service

Every service.
Room to run.

One sandbox foundation for all your services. Give each workload its own environment while your products own the experience.

Explore the platform Read the docs

Internal preview for trusted operators.

Many services. One foundation.
Consuming service01
nanohub / repository job
Isolated sandbox02
~ /sandbox/workload→ compute · storage · network
Space for the next idea
Service accessA workload endpoint
Your services → Condensation → SandboxesInfrastructure illustration

One shared foundation.

CodegraffnanohubYour next project

01 / The platform

One foundation.
Every workload.

Condensation owns the sandbox lifecycle. Each consuming service owns its repositories, agents, deployments, and application logic.

01 / Provision

Sandbox lifecycle.

Create an environment for a workload, inspect it, and remove it when the job is done. A common infrastructure boundary from the start.

Explore the architecture
02 / Run

Workload resources.

Compute, guest storage, and network access belong to the sandbox layer. Nanohub and Codegraff supply their own application behavior.

Read lifecycle guidance
03 / Attribute

Service-level visibility.

The dashboard design groups sandboxes by consuming service, with resource details and usage estimates. Live metering is the next step.

Explore the dashboard

A look inside / Dashboard preview

Your sandbox fleet, in view.

One inventory across your services. Filter sample sandboxes by state and service, then inspect their resources and usage.

Explore the dashboard
Condensation lab OverviewSample data

Your space to build

One fleet. Every service.

Sandbox state, resources, and usage across all your services.

Explore dashboard
SandboxState
Interactive design preview · Sample sandboxes, no live fleet connection.

02 / A small, familiar API

A small API.
Room to do more.

The shared sandbox layer is the product boundary. Today’s operator API still exposes workload-specific adapters; a generic sandbox API is planned.

Read current API docs
Trusted internal operators
condensation / quickstartHTTP
POST /v1/apps
curl https://sandbox.condensation.ai/v1/apps \
  -H "Authorization: Bearer $CONDENSATION_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"name":"hello","title":"My first preview"}'

Creates a static Python-served preview and returns its named HTTPS address.

Use your operator key to run a request.

Proposed launch pricing / USD

More room to run.
Less spent on compute.

One usage model across every consuming service. No per-seat fee. These are proposed rates; public billing and checkout are not available yet.

Usage

$0 / month platform fee

Start without a commitment. Pay for the sandbox resources you allocate.

  • $0.030 / vCPU-hour
  • $0.010 / GiB-hour of memory
  • Proposed per-second compute billing
  • Same rate across consuming services

Committed

$250 / month minimum spend

For predictable workloads. The commitment covers usage; it is not an extra platform fee.

  • 15% off CPU and memory
  • $0.0255 / vCPU-hour
  • $0.0085 / GiB-hour of memory
  • Unused commitment expires monthly

Dedicated

Custom / capacity agreement

Plan a dedicated pool for sustained demand across your services.

  • Capacity and term priced together
  • Hardware and region agreed upfront
  • Support requirements scoped separately
  • Subject to capacity review
Estimate your usage and compare providers

03 / Start with our own work

Our projects.
Our infrastructure.

Condensation is a common home for the environments behind Codegraff, nanohub, and what comes next. We’re building it against real work, starting with our own.

Internal preview / No public sign-ups

Before you get started.

Built for the work ahead.

Your next idea.
A place to begin.

Give your next service a sandbox foundation.
Start with the operator API.

Read the operator docs