Dedicated instances

Standards is hosted at api.standards.new. On request, we run an instance on isolated servers dedicated to one organisation. Nothing else changes: the same SDK, the same CLI, the same MCP surface, under a hostname of yours.

The only setting that moves is baseUrl:

import { createStandards } from "@stndrds/client";

const standards = createStandards({
  // https://api.standards.new/v1 on the shared host; your own hostname on a dedicated instance.
  baseUrl: process.env.STANDARDS_API_URL!,
  apiKey: process.env.STANDARDS_API_KEY!,
});

The CLI stores one profile per instance: standards login --name production --url <your hostname>, then --instance production on any command. An MCP client uses the same /mcp path under your hostname.

When to ask

• Data residency: your records must stay in a region or on servers of your choosing.
• Compliance: an audit requires isolation from other tenants.
• Volume: a sustained workload you would rather size on its own servers.
• Custom connectors: integrations that only make sense inside your network.

Write to [email protected] with the organisation, the region and the workloads you have in mind.

Next steps

• SDK: createStandards and its options.
• CLI: instance profiles and --instance.
• MCP: connect Claude Code, Codex or Cursor to your host.