Skip to content
Subnomic
Start free
Sites, Storage, Registry, Workflows and AI — one workspace

Ship a site, store the bytes, push the image.

Subnomic is one workspace for hosted static sites, S3-compatible object storage and a container registry — plus an agent that can act across them and shows every step it takes. One bill, one set of credentials, one audit log.

Start free — no card Read the docs
Free plan
no card
Storage API
S3-compatible
Registry
OCI distribution

Five products, one workspace

Each one is finished on its own.

Nothing here is a checkbox next to a bigger product. Storage speaks S3 to any client that speaks S3, the registry is the OCI distribution API, and a site is a URL with a rollback behind it. They share a workspace, a bill and an audit log — not a compromise.

Sites

Static hosting with a real rollback

Push a directory, get a URL. Every deployment keeps its own immutable preview address, so rolling back is promoting a deployment that already exists rather than rebuilding the one that worked.

~/acme-site
$ subnomic sites deploy --prod
Hashing 148 files (18.7 MB)…
312 files already stored, 14 to upload.
https://blog.subnomic.app
  • Your own domain with two DNS records — a CNAME to cname.subnomic.app, and the certificate follows.
  • Per-deployment redirects and headers, versioned with the files they apply to.
  • Privacy-first traffic numbers: no cookie, no visitor identity, no third party.
Look at Sites

Storage

S3-compatible object storage

The endpoint and the key are the product, so they are the first thing on the page rather than four clicks in. Any client that speaks S3 speaks to this — the AWS CLI, rclone, restic, the SDK you already have in the repo.

region eu-west-1 · path-style addressing
$ aws configure set region eu-west-1
$ aws --endpoint-url https://s3.subnomic.com s3 ls
2026-08-21  acme-db-dumps
2026-08-04  acme-cdn
  • Versioning and object lock, with the locked window stated in days on the object itself.
  • Access keys can be scoped to buckets, a prefix and read, write or delete — and the secret is shown once.
  • A bucket anyone can read without a credential says so, in ink, before you open it.
Look at Storage

Registry

A private OCI registry that scans

docker login and you are done. The supply-chain state — what is signed, what is vulnerable, and which version fixes it — is readable from the list, not behind a tab somebody has to remember to open.

registry.subnomic.com
$ docker login registry.subnomic.com -u acme
$ docker push registry.subnomic.com/acme/api:1.4.0
The push refers to repository [registry.subnomic.com/acme/api]
  • Every push is scanned, and each finding names the version that fixes it.
  • Cosign signatures are recognised as signatures, not listed as stray tags.
  • Robot accounts for CI, scoped to one repository and revocable on their own.
Look at Registry

AI

An agent with your workspace in reach

Ask it a question about the workspace and it reads the workspace to answer. Every tool call is shown with the real arguments it was called with, and it never holds more permission than the person who gave it access.

Running Why does api in prod-eu keep restarting?

crashloop_report namespace=prod

kube_logs pod=api-7d9f5c-x2k8q previous=true

Waiting for you

rollout_restart on api was proposed from the incident. It runs only after somebody approves it.

Look at AI

Workflows

The four of them, wired together

Draw a graph of the things you already let people do by hand — read a database, restart a deployment, ask a person — and run it on a schedule, a webhook or a button. Each workflow runs as its own credential, so it can never reach further than whoever wrote it, and every step is in the same audit log as everything else.

  • A run survives the worker that started it: succeeded steps are not run twice, so a restart never sends the same command again.
  • Anything that changes something can stop and wait for a person, and editing the graph asks for approval again.
  • Describe it in a sentence and the graph is drawn for you, on the canvas, where you can argue with it.
Look at Workflows

The decisions behind it

Three habits you will notice by the second day.

A limit is a sentence

Not a bar at 86%. A quota says what it is and how close you are, in words — so nothing is a surprise at 3am.

Objects 214,300 / 250,000

214,300 of the plan’s 250,000 objects. Nothing already stored is ever deleted.

Public is inside-out

Exactly one thing in the product is drawn inverted, and it always means the same thing: somebody with no credential can reach this. You never have to open a policy to find out.

Public to anyone Private Object lock · 30 days

The same pill marks a public bucket wherever it appears, and it is the only inverted element anywhere.

Every value is grabbable

Endpoints, keys, digests and DNS records are chips you click anywhere on — a value you are meant to take away should not ask you to aim at a 14px icon.

Try one — it really copies.

Fleet

When the servers are yours too.

The same workspace grows a second tier: your own servers and Kubernetes clusters, reached through an agent that opens no inbound port. Servers start on Pro, guardrails and session recording come with Team, and just-in-time access with Enterprise — so the fleet grows with the plan rather than hiding behind a dozen padlocks on the nav.

Servers

CPU, memory and disk as three bars, and a governed terminal on the page.

Kubernetes

Replicas as ready over desired, and right-sizing from the P95 of sampled usage.

Incidents

The timeline is the incident, and the proposed fix waits behind a human.

Compliance

Access reviews signed off in one place, and an audit chain that states its limits.
Look at Fleet Talk to us about Fleet →

Before you sign up

The questions we would ask.

Where does my data live?

Objects are stored in eu-west-1. The region is on the storage page in the console, not in a support article.

Can I leave?

Storage is S3 and the registry is the OCI distribution API, so leaving is aws s3 sync and docker pull — the same two commands you would have used anyway. That is the point of standard APIs.

What does the AI actually see?

Only what its access is scoped to — never more than the person who created that access can do — and every step is shown with its arguments. A guardrail that requires approval refuses the call instead of running it.

Is the free plan a trial?

No. It needs no card and does not expire — one site, 512 MB of storage, one member. Reaching a limit never deletes anything already stored.

Do I have to use all four?

No. Most workspaces start with one. The others are there when you need them, on the same bill and behind the same credential.

Who can see what?

Roles are per workspace, sessions are listed and revocable one at a time, and the things a stranger can reach without a credential are drawn inverted so you can find them by looking.

A workspace, an endpoint and a namespace — about a second from now.

Signing up creates all three and tells you what they will be called before it does it. The free plan needs no card.

Start free Read the docs