What is sold here is mentorship, so the site is not a course. No modules, no lesson numbers, nothing to complete — a decision the interface has to keep in every place a progress ring would have been the obvious component.
Around that sit the three things a member pays for and a stranger must not reach: the recordings, a protected player, and a journal for their own trades. The whole build is the machinery for letting exactly the right people through one door — and for being straight, on every screen, about what it does and does not know.
Five of the six member pages answer a stranger with a redirect. You can open the front door of EXECUTED yourself; you cannot open these.
Stamped before the page is sent
Written in by the middleware that already checked the session — no extra request, no flash of a placeholder, and nothing a client-side toggle can undo.
Nothing leaves the browser
Statistics are computed where they are read and the log is stored locally. Importing a year of trades makes no request at all: a privacy property first, a cost property second.
Metered on writes, not bandwidth
Session touches throttled to one per ten minutes, and the static half of the site routed around the worker entirely. That turned a launch-day quota ceiling into a rounding error.
The build refuses to ship
A member page slipping out of the gate fails the build, as does a route rule that would let one bypass it. Every guard was checked by feeding it a wrong input and watching it fail.
EXECUTED publishes no performance figures. No win rates, no returns, no equity curves — not its own and not anybody else's. It is written into the product's footer, and it is the most useful constraint in the build.
It removes every element this category normally reaches for: the results banner, the profit screenshot, the ticker of members' wins. What is left has to persuade on substance. It decides small things too — the accent is red, and in this industry red is the loss colour, so it is chrome and never sits beside a number.
The same rule governs this page. A case study is supposed to answer what did it achieve, and for a trading product every tempting answer is one the product itself refuses to make. So the claims here are engineering ones: it ships, it is gated, and the gate is checked against production on every deploy.
The public page is open to anyone — executed.xyz. The member area is not, and the plates above are the only way to see it without a membership. Every screenshot is of the real build; the numbers inside them are the product's own sample data, which it stamps as such.
Something behind a login?
Gated products are their own kind of job — the half nobody sees is the half that has to be right. Tell me what you're building.
hello@studiokiln.space- Tell meWhat you're building, roughly when you need it, and a link or two you like.
- You'll hear backWithin 48 hours, from me. There's nobody else here to route it through.
- You'll getA tier recommendation, a timeline, and a fixed quote. No hourly billing.