Say what you
will deploy.

Access opens a deployment end to end: your brand, your regime, your tenant, signed from your own developer account. The address comes first; the one question after it is optional.

Get started.

An address, and one optional question about the building you run. Access is provisioned from this list.

Which operator are you? (optional) A DC, a plant or a yard — I run the building. A 3PL or a cold-chain custody operation — I run it for customers. A store network — receiving, backroom, floor. A union, a trade school, an apprenticeship program, a trade association — an instance for our own members.

Access is provisioned from this list. We use your address to tell you when yours is ready and to follow up about it; you can tell us to stop at any time. We don't sell it or hand it to advertisers. If we stop working on this, we say so rather than go quiet.

The row is what you give it — address, timestamp, the one answer if you give it — plus a token we mint for that row. Nothing derived from the request is stored on it. Separately, this origin does record the request itself — the referring page, the user agent, the address and the network it came from, and whether we judge the caller a person, an agent or a crawler. That is its own store: what we log, in full.

Read before you sign up, if you prefer.

What a deployment is and is not is on the door; the arguments are on the blog; the full product document is /product.md; the verbs the app is built on are at worklists.dev.

Say what youwill deploy.

Get started.

Read before you sign up, if you prefer.

Say what you
will deploy.