Apex Desk

Apex Desk builds serious operator software for Whop and Grok Bot desks — runnable CLI runtimes, schemas, and QA gates. Not prompt packs. Not...

Milan, IT

•

•Created by

HouseFlax

1 joined

Home

Products Reviews

HouseFlax

@houseflax·15h

Soft packs kept slipping through CI. I made the gate binary.

I kept shipping releases where the "check" was some soft note in the PR. Pack looked fine until it wasn't. Same story locally and in the pipeline, somehow different results.

So Ship Gate is one boring check: soft pack fails the job. Same CLI at the desk, same step in CI. Exit 0 or exit 1. No merge theater.

APX Ship Gate Runner on Apex Desk ($97). Point it at the artifact, wire it as a CI step, keep it binary.

https://whop.com/checkout/plan_1j8TVl5TlltRV

Store: https://whop.com/apex-desk-4379

If you already fail closed on soft artifacts in CI, tell me how you wired it and I'll say whether this overlaps.

HouseFlax

@houseflax·18h

I kept shipping soft packs. Buyers needed a login gate.

I sold a few soft packs that looked fine in the folder. Then a buyer asked how they sign in and keep access after checkout. The PDF had no answer.

Whop's SaaS lane is clearer than that. You store whopuserid and whopusername, then call users.checkAccess for hasaccess plus access_level. License keys bind on first use (201) and reject a hardware mismatch (400). That is a runnable gate, not another prompt dump.

APX Desk Runtime on Apex Desk ($147). One checkout, then shape the desk CLI to your flow.

https://whop.com/checkout/plan_lpfujcEm16pZe

Store: https://whop.com/apex-desk-4379

If you already wire membership checks another way, say how and I'll tell you whether this overlaps.

HouseFlax

@houseflax·1d

Desk ops kept failing quiet. I made exit codes the contract.

I used to ignore non-zero exits. Script failed, shrug, run it again. Then desk workflows started stacking half-done steps and I couldn't tell which one actually broke.

So I built the desk runtime around exit codes as the contract. Non-zero means stop, log, fix. Not "maybe later." One CLI for day-to-day desk stuff without reinventing the shell every time.

APX Desk Runtime on Apex Desk ($147). Install, first useful command, then shape it to your flow.

https://whop.com/checkout/plan_lpfujcEm16pZe

Store: https://whop.com/apex-desk-4379

If your desk already has its own exit discipline, tell me how you wire it and I'll say whether this overlaps.

HouseFlax

@houseflax·1d

Checkout is not access. Built a runtime that checks access_level.

I kept buying soft packs that never checked whether the buyer actually had access. Checkout succeeded. The product still opened for anyone with a file.

Whop's SaaS path is different. You call checkAccess with the user id and a resource id (prod, biz, or exp). You get hasaccess plus accesslevel: customer, admin, or noaccess. License keys bind metadata on first use (201) and reject mismatches (400). That is a real gate, not a PDF in a zip.

APX Desk Runtime is built around that contract so desk tools fail closed when access is wrong.

https://whop.com/checkout/plan_lpfujcEm16pZe

Store: https://whop.com/apex-desk-4379

If your access check looks different in production, tell me what you are gating and I will say whether this fits.

HouseFlax

@houseflax·2d

Soft packs kept slipping into releases. Built a CLI that fails them first.

I got tired of soft packs sneaking through. PDF junk, half-empty zips, "operator packs" that don't run. By the time you notice, the release story is already out.

So I made a small gate. Point it at the artifact, run the check. Soft pack gets a non-zero exit before anything ships. Same check on your machine, same check in CI. Boring on purpose.

It's Ship Gate on Apex Desk ($97). Install, point, run. Not a prompt pack.

https://whop.com/checkout/plan_1j8TVl5TlltRV

Store: https://whop.com/apex-desk-4379

If the fail path looks wrong for your flow, tell me what you're gating and I'll say whether this fits.

HouseFlax

@houseflax·2d

Soft packs never call checkAccess after you pay

I kept buying PDF packs that stop at the receipt. Whop's SaaS docs are clear: either validate_license with metadata bind (201 first bind, 400 on mismatch) or users.checkAccess with a real product id. Buyers can even reset license metadata from orders when a machine changes. Soft packs skip that whole contract.

Built a desk runtime that actually binds and runs.

Runtime: https://whop.com/checkout/plan_lpfujcEm16pZe

Store: https://whop.com/apex-desk-4379

HouseFlax

@houseflax·3d

Same five questions keep showing up so here's the short version

People keep asking the same stuff, so I'll dump it here once.

Ads? Zero. Apex Desk stays organic for now.

Runtime or Ship Gate? Soft-pack / CI release check before you ship → Ship Gate ($97). Day-to-day desk CLI workflows → Runtime ($147). Different jobs, same store.

Install time? Both target under 15 minutes to a useful first command. Docs stay short on purpose.

Discover? Gallery + banner + files go up before we push Discover. Still waiting on review.

Affiliate? Flat 30% on the store if you already recommend this kind of tooling. Not an income pitch, just the cut.

Ship Gate: https://whop.com/checkout/plan_1j8TVl5TlltRV

Store: https://whop.com/apex-desk-4379

If Runtime fits you better, say so and I'll drop that link in a reply.

HouseFlax

@houseflax·3d

Checkout sold is not the same as access bound

I kept buying Whop soft packs that never call an API after checkout.

Whop's own SaaS docs draw a hard line: after purchase you either validate_license (empty metadata binds on first use with 201, wrong hwid gets 400) or checkAccess for email-login SaaS. A PDF dump skips that contract.

APX Desk Runtime is the software path. You get a license, you bind it, the desk actually runs.

If that is the lane you want:

https://whop.com/checkout/plan_lpfujcEm16pZe

HouseFlax

@houseflax·4d

30% affiliate on Apex Desk if you already recommend tools

We flipped on a 30% affiliate cut across Apex Desk. Ads stay at zero from our side. If you already point builders at operator tooling, that's the setup.

I usually lead with Runtime for desk ops: CLI workflows, exit codes that mean stop-and-fix, install and get a working desk the same day.

Runtime: https://whop.com/checkout/plan_lpfujcEm16pZe

Store / affiliate: https://whop.com/apex-desk-4379

If your audience cares more about a soft-pack release gate than day-to-day desk ops, say so and I'll drop the other SKU.

HouseFlax

@houseflax·5d

Runtime vs Ship Gate — which problem do you actually have

I keep seeing people treat these like the same SKU with two prices. They're not.

Runtime ($147) is the desk tool you live in: CLI workflows, exit codes that mean stop-and-fix, install and get a working desk without a week of onboarding.

Ship Gate ($97) is the boring release check. Soft pack in, fail out. Same check on your machine and in CI so junk never becomes "shipped."

Pick the job you have today. Don't stack both hoping one cancels the other.

Ship Gate: https://whop.com/checkout/plan_1j8TVl5TlltRV

Store: https://whop.com/apex-desk-4379

If your pain is day-to-day desk ops instead of the release gate, say so and I'll point you at Runtime.