Start building with Namespace - Namespace Documentation

Documentation Index

Fetch the complete documentation index at: /docs/llms.txt

Use this file to discover all available pages before exploring further.

Assistant

Responses are generated using AI and may contain mistakes.

Build directly on Namespace for your own workloads, or build a platform that runs workloads for your customers, each in their own isolated tenant.

Build a platform \ \ Give each customer a tenant, and act inside it on their behalf.

Run workloads \ \ Create your first instance with your nsc login.

TypeScript

curl

const created = await computeClient.compute.createInstance({
  shape: {
    virtualCpu: 2,
    memoryMegabytes: 4096,
    machineArch: "amd64",
    os: "linux",
  },
  documentedPurpose: "quickstart",
  deadline: timestampFromDate(new Date(Date.now() + 60 * 60 * 1000)),
  containers: [\
    {\
      name: "demo",\
      imageRef: "busybox",\
      args: ["sh", "-c", "echo hello from Namespace"],\
    },\
  ],
});

resp, err := computeClient.Compute.CreateInstance(ctx, &computepb.CreateInstanceRequest{
    Shape: &computepb.InstanceShape{
        VirtualCpu:      2,
        MemoryMegabytes: 4 * 1024,
        MachineArch:     "amd64",
        Os:              "linux",
    },
    DocumentedPurpose: "quickstart",
    Deadline:          timestamppb.New(time.Now().Add(1 * time.Hour)),
    Containers: []*computepb.ContainerRequest{{
        Name:     "demo",
        ImageRef: "busybox",
        Args:     []string{"sh", "-c", "echo hello from Namespace"},
    }},
})

curl -sS -X POST "$COMPUTE_API/$SERVICE/CreateInstance" \
  -H "Authorization: Bearer $NSC_TOKEN" \
  -H "Content-Type: application/json" \
  -d @- <<JSON
{
  "shape": {
    "virtualCpu": 2,
    "memoryMegabytes": 4096,
    "machineArch": "amd64",
    "os": "linux"
  },
  "documentedPurpose": "quickstart",
  "deadline": "$DEADLINE",
  "containers": [\
    {\
      "name": "demo",\
      "imageRef": "busybox",\
      "args": ["sh", "-c", "echo hello from Namespace"]\
    }\
  ]
}
JSON

The same call works in both cases. Only the credential behind computeClient changes: your nsc login while you develop, or a tenant token when your platform acts for a customer. See the Instances quickstart for the full call, including authentication and waiting for the instance to become ready.

Authenticate

Every call authenticates with a credential that decides where it acts. While you develop, your nsc login acts in your own workspace. A platform uses partner credentials to manage its tenants, and tenant tokens to act inside each one.

Build on your own workspace \ \ Start with your nsc login, no partner account needed.

Partner credentials \ \ Authenticate as your platform to manage tenants.

Tenant tokens \ \ Act inside a customer’s tenant.

Building blocks

Pick the infrastructure that fits your stack.

Compute \ \ Linux and macOS machines, shapes, resource limits, and observability.

Networking \ \ Ingress, access controls, egress policy, and performance.

Storage \ \ Cache volumes, the container registry, artifacts, and secrets.

The full API reference is at API and SDKs.

Last modified onOctober 2, 2026

Ctrl+I

Documentation Index

​ Authenticate

​ Building blocks

Authenticate

Building blocks