← SkillSafe / Launch Gate

Clear the launch before it ships

Paste the launch brief and a short facts block. Get the three answers an approver actually needs: which regulations and approvals apply, how bad the exposure is and what evidence has to exist — over one work object, in one sitting, with each lane able to start from the last one's output.

Both examples ship with a saved model run, so you can see a full clearance — the frameworks, the risk matrix, the register — without signing in and without spending a credit.

1. Scope
2. Decide
3. Produce

1. Scope

What applies

nothing pasted yet
Drag a file in, or Everything is read in your browser. Nothing uploads until you run.
no facts block yet
Every line is optional. regions: and data: change the answer more than the rest put together.
Paste the launch brief to begin.

What this does, and what it does not

The scan is a real key: value reader, not a keyword search. Keys are normalised and aliased, so Jurisdiction, regions and markets all land on the same field; indented and bullet lines continue the key above them, so a long processor list can run down the page; a second processors: line is merged rather than treated as a correction; and a line that is neither is reported rather than dropped. That is what lets it tell apart cases a grep cannot: transfers: none switches the cross-border signal off even when a stray sentence says "hosted in the US", while dpa: all signed is read as a blanket statement covering every vendor rather than as "unknown for all of them".

Frameworks are placed by rule from the jurisdictions you declared, the standards you named and the behaviour the brief describes — never because a topic is adjacent. Approval gates come out the same way, each with a required, likely or no call and the role that owns it. Everything the scan finds is handed to the model as facts it must account for one by one, and the reply is checked back against them: if the model skips a flag, this page says so and the flag stays open.

It reads; it does not decide. This is a working analysis for a named human — privacy counsel, security, or the accountable owner — to review. It is not legal advice, not a clearance, and not a substitute for the assessment it will tell you to run. It states no fee, no fine and no statutory deadline in days, because a stale number is worse than none. A credential you paste is a credential you should rotate: the scan names it and neither the page nor the model repeats it back.

Nothing to hand? Load the , a nightly model that auto-downgrades accounts across the EU, the UK and California, or the , a customer-facing claims flow in Brazil and Canada with bank details in it. Both replay a saved run for free. There is also a if you would rather edit than read.