The Sandbox. Here’s what it actually is.
You’ve seen the button. People keep asking — fair enough, we never explained it. The Sandbox is a seat next to the engine we built to run this company’s work. Calling it “pipeline access” undersells it: what you’re buying is the expertise the engine was trained on — twenty-five years of how Jade and Tim actually build, run at machine speed.
What a seat buysYou’re not buying compute. You’re buying the bench.
The expertise is the product — the engine just delivers it+
Anyone can rent a chatbot for twenty bucks. That gets you a machine that answers. What it doesn’t get you is twenty-five years of knowing which answer is the buildable one — the judgment about what to make, what to skip, and what to never trust the machine with.
That’s what the Sandbox actually is. We built an engine — a tiered fleet of stations that draft, flag, challenge, and check each other — and then we spent years teaching it how we work. Not prompts. Interactions. Corrections. The way a senior dev leans over a junior’s shoulder, except the junior got faster instead of offended.
So a seat isn’t “use our tools.” It’s your idea run through the same filters that run ours — with the humans who built them still holding the gates. (The plumbing itself is public: how the stations talk to each other.)
Every one of those passes costs real money. That’s the honest reason seats aren’t free.
Why it costsThe meter is real. That’s the whole reason it works.
Metered filters · pricing TBD · queue open+
Running the engine costs money — ours, every single run. Even pushing one idea through means it processes across filters the whole way down, and some of those filters are metered: we get billed per pass the same way a shop gets billed for machine time.
So yes, Sandbox access will be paid. We haven’t set the fees yet — we’d rather ship pricing that’s honest than a number that sounds good in an ad. What we can tell you: the queue is open now, joining it is free, and it’s the order we onboard.
And the meter is a feature, not a bug. Free tiers teach you to accept whatever comes back. A metered run means the engine actually worked your idea — challenged it, cleaned it, shaped it — instead of handing you the first draft and a smile.
Fees TBD. When they’re set, the queue hears first.
Proof, not promisesEverything we shipped this year went through it first.
The Gazette · Scan Quest · the games shelf+
We’re proving the concept with our own catalog before we sell anyone a seat. The Gazette, Scan Quest, the games shelf — all of it ran through the engine. Not prototypes on a pitch deck: live products you can open right now. And what you’re seeing is the warm-up — the same engine is pointed at bigger leagues than the 209.
A full regional news and directory operation — issues, events, eats, city guides — built and run through the engine.
Open it →Game platform · liveScan QuestQR-driven scavenger-hunt platform with accounts, economy, vault, and a paid gem store — through the engine, start to finish.
Open it →Games shelf · liveEAS Free GamesThe public games shelf — Scan Quest, Touchless Egg Hunt, Orginz Trail — plus The Epic Game Book, the house field guide.
Open it →That’s the pitch: if you’ve watched what we’ve put out over the last twenty-five years — that’s what a seat gets you. Same bench, same standards, faster hands.
Not a vending machineWe didn’t pay $20 and drop a prompt in either.
The engine learned how we build — because we made it+
Here’s the part the AI crowd won’t tell you: you cannot drop information into a box and get what we get. We know because we couldn’t either. Getting this engine to build the way we build meant working every station by hand — correcting drafts, arguing with outputs, rejecting the confident wrong answer until the right one survived.
That’s the difference a seat buys. The engine learned from our interactions — how Jade scopes, how Tim gates, what we reject and why. It builds like the two of us now, just faster. And when you’re in the Sandbox, you work it the same way: you interact, it learns your project, humans hold the calls.
If that sounds like work — good, it is. It’s just a different kind of work than staring at a blank page. The machine does the typing. You do the thinking, the checking, and the shipping. Same division of labor we run internally.
No — and walk away from anyone who says their box can. Sandbox seats are guided, gated working sessions. You steer; the engine drives fast.
Your run is your run. If you want paper first, the free mutual NDA is at /agreements/ — public, plain, and you don’t have to ask permission to use it.
Soon — that’s the honest answer. The engine runs our own work today; paid seats open when the billing’s as solid as the bench. The queue is the order.
“You’re getting twenty-five years of shipped work — at a discount, because we’re not dicks.”— The Captain, Epic App Solutions
Request a sandbox seat.
Joining the queue is free; seats won’t be. Fees aren’t set yet — when they are, this list hears first, in the order requests came in. Tell us what you’d run through the engine and we’ll take it from there.
Same gate as the rest of the site: business email required — public providers don’t enter the sandbox queue. No company domain yet? The Dreamy bubble on the homepage is open to everyone, or ask us for help getting set up.
Don’t send passwords, keys, or anything you’re not authorized to share. Sensitive first? Build the free NDA before you disclose.
Want it built for you instead?
The Sandbox is for teams who want to work the engine themselves. If what you actually need is a finished product — the case, the build, the polish, the sale — that’s the normal lane, and it starts with a case file instead of a queue.
One hour of consultation is on us either way. After that we’re developing — not pitching.