What we ship and why we ship it here.

Products, not features.

Each thing that lives at <name>.claw.site is a product. It has its own name. It does one thing for one kind of person. It has a price, a paywall, an onboarding, a dashboard, and a reason a person would return to it on day thirty. If any of those is missing on launch day we either build it or we hold the launch. We do not ship landing pages and call them products.

The studio is the place a product is allowed to grow up; it is not a hosting plan and it is not a portfolio. A product that's only here because the infrastructure is convenient gets pruned.

One platform, hard boundaries.

Sharing infrastructure is a deliberate trade. The upside is that the unpriced work — auth, billing, observability, schema migrations, backup, SOC-style review — gets done once instead of N times. The downside is that one product's users can in principle reach another product's data if a boundary slips. We refuse that downside by putting the boundary in the database itself: each row carries the product it belongs to, and every read is filtered through a policy that knows which product the caller is talking to.

The codebase boundary is comfortable but soft. The database boundary is uncomfortable but survives a careless commit. We pay the cost of the second one.

AI is in the toolbox, not on the marquee.

The products under this roof use language models the way they use a database: as a tool to deliver a specific outcome for a specific person. The marquee is the outcome — a person finishing a piece of shadow work, a person tracking their hairline over twelve months, a person clearing their inbox without doomscrolling. The model is how we get there. When the model changes, the outcome doesn't. We are not in the business of selling someone a chat window.

A product whose only answer to “what do you do?” is the name of a model has not finished defining itself.

Editorial discipline. No SEO chaff.

We do not stamp out programmatic pages, listicles, AI-spun blog posts, or coming-soon teasers to fill a sitemap. Every page on the studio and every page on a product subdomain is written for a person we'd like to keep around. If a section of the site would embarrass us to read aloud, we don't publish it. New apps stay out of the public catalog until they have real content and a real reason to exist.

That includes the studio. This page is short because it has to be.

What we won't do.

• No marketplace. The studio does not host other people's apps. The roof is for the team who maintains it.
• No tracking we wouldn't opt into. Each product knows what its own users do inside it. Nothing is shared across products without saying so out loud, and we do not share with anyone outside.
• No growth hacks. If a tactic would feel insulting on the other side of the email, we don't ship it.
• No retroactive content rewriting. What we said yesterday stays said. If it's wrong we publish a correction; we don't edit it out.