For makers

Make one

Owhile runs on things people built because they wanted to see what would happen.

Here is how it goes. You write down who it is for and what they may be shown — that is the profile, and it is the only hard part. Everything after that is derived from it: the template you fill in, the checks that run, the report that gets you on the board.

A machine reads your work before we do.

Not a review panel, not a queue, not us reading it over a weekend. A set of checks that either pass or do not, and tell you exactly what failed and where. The same checks for everyone, including us.

You keep your thing.

Host it yourself if you would rather. Either way it goes on the board here — that is the part that is always Owhile.

What we can promise, and what we cannot.

We can promise the tools, the checks, and a place on the departure board. We cannot promise you an audience, because right now there is not one. Owhile opened this month. If somebody tells you otherwise about a new platform, they are guessing.

Owhile is for grown-ups.

Experiences built for children do not go on this board. That is not a taste judgement — a general catalogue with children in it is a different kind of thing with a different set of duties, and we are not that. The check is automatic and it fails closed: no declared minimum age, no listing.

Setting it up

The fastest way in is to hand this to a coding agent. Point it here:

owhile.vercel.app/llms.txt

It will read that, install the tool, and walk you to a first batch that passes the checks. You will be answering questions about who your thing is for — that part is yours and cannot be automated, because it is a judgement rather than a config file.

Prefer to do it yourself? The same page reads fine as instructions.

Start