ss catalog — browse providers & pricing

ss catalog shows everything Starsystem knows how to deploy or connect to — from Postgres databases to domain registrars to email providers — with pricing and the YAML snippet to wire them in.

ss catalog                             # all providers and services
ss catalog --category=dns              # filter to DNS / domain providers
ss catalog --category=database         # databases with pricing tiers
ss catalog --mode=provision            # only deployable providers (no SaaS pricing)
ss catalog --mode=browse               # only SaaS pricing (no deploy info)
ss catalog --json                      # machine-readable output

Two sections

Deployable providers

Providers that ss deploy or ss provision can manage directly via API. Each entry shows:

What resource types it handles
Which vault keys it needs
An example YAML snippet you can paste into starsystem.yaml

Provider	Resources	Vault keys needed
`neon`	postgres	`neon.api_key`
`supabase`	postgres, database	`supabase.api_key`
`fly`	app, container, worker	`fly.api_key`
`railway`	app, container, worker	`railway.api_key`
`cloudflare`	pages-project, workers-kv, d1-database, r2-bucket	`cloudflare.api_key`
`aws`	s3-bucket, cloudfront, s3-cloudfront	`aws.access_key_id` + `AWS_SECRET_ACCESS_KEY`
`porkbun`	domain, dns-zone	`porkbun.api_key` + `PORKBUN_SECRET_KEY`
`local-process`	process, app, worker, server	none

Services & pricing

Browseable SaaS services with monthly pricing from the resource catalog. Useful for comparing tiers before committing. These services are referenced in YAML as type: external with appropriate credential_env values — Starsystem doesn’t provision them, but it models the connection and manages the credentials.

Categories available:

Category flag	What’s in it
`auth`	Clerk (free / pro), Auth0
`email`	Resend, Postmark
`payments`	Stripe
`storage`	Cloudflare R2, Backblaze B2, Tigris
`queue`	Upstash QStash, Inngest, Trigger.dev
`database`	Neon tiers, Upstash Redis
`observability`	Sentry, Axiom, Betterstack
`dns`	Porkbun domains (.com, .io, .dev, .ai, …)
`compute`	Hetzner VMs (CX22 through CCX63)

Examples

See what you need to deploy a domain

ss catalog --category=dns

DEPLOYABLE PROVIDERS  — ss deploy wires these up automatically

  porkbun  Porkbun
  Domain registration and DNS management — register domains and wire DNS records automatically.
  Resources: domain, dns-zone
  Vault keys: api_key, PORKBUN_SECRET_KEY

SERVICES & PRICING  — drag onto canvas or reference in YAML

  Porkbun Domains
    .com                           $0.88/mo · $9.73/yr first year, $10.57/yr renewal
    .io                            $2.99/mo · $35.88/yr renewal
    .dev                           $1.04/mo · $12.49/yr renewal
    .ai                            $5.83/mo · $69.98/yr renewal

Compare database options

ss catalog --category=database --mode=browse

Get machine-readable output for scripting

ss catalog --json | jq '.provisioners[] | {provider, resources}'

Connecting a service from the catalog

Run ss catalog --category=<cat> to find a provider
Copy the example YAML from the catalog output
Add it to your starsystem.yaml

Store the required vault keys:

ss vault set-key <provider> api_key <your-key>

Run ss provision or ss deploy --env=<env>

For SaaS-only services (Stripe, Clerk, Resend, etc.), add them as type: external services and store their credentials in the vault — Starsystem tracks the connection and exposes the env vars to dependent services.

MCP access

Agents can query the catalog without shell access:

starsystem_catalog
→ returns { provisioners: [...], catalog: [...] }

starsystem_catalog category="dns"
→ filtered to DNS providers and domain pricing

Use starsystem_catalog before starsystem_add_service to pick the right provider and get the correct YAML shape.