Buying and Installing: One-Time Price → an Install Link

In short

The monetization model is a single one-time payment with no subscriptions: the base engine is 4 900 ₽ forever, modules are 1 900 ₽ each; browsing the catalog, assembling and previewing are free. Payment goes by card through YooKassa (a Russian payment provider): once the payment is confirmed, the system issues your personal install link /install/<token> on its own, with a package built for your tool (Claude Code, Cursor or AGENTS.md), a README and an installer prompt. YooKassa webhooks aren't taken at their word — the status is re-checked against the API, and processing is idempotent, so there's never double processing or two tokens. The license is counted by install seats; the version you bought stays yours forever — a new core ships as a separate product, not as a "subscription upgrade".

What it is. The monetization model is simple and subscription-free: one payment for one engine. No credits, no wallets, no recurring fees. Browsing the catalog, assembling or picking an engine, and flipping through previews are free; you pay only for DELIVERY of the installable package.

One-time payment → an install link with a seat limit

Why this way. Configs are a commodity — there's no shame in showing them. The value is in the assembled discipline of a vibe-coding engine (a team of roles + veto reviews + process + installer); modules extend the engine and are bought the same way, with a one-time payment. The version you bought is yours forever; a new core version ships as a separate product, not as a "subscription upgrade". That's why the paywall sits at the delivery boundary rather than on routes: without paying you see a redacted preview, but not the full spec and not the package.

What it costs. The price is visible right on the engine's card before you buy: the base engine is 4 900 ₽ as a one-time payment and yours forever, modules are 1 900 ₽ each. Pay by bank card through YooKassa and your personal install link is ready.

4 900 ₽

base engine — one-time payment, yours forever

1 900 ₽

module — also a one-time payment

0 ₽

catalog, assembly and previews — no subscriptions, no credits

Prices are visible on the engine card before purchase; payment by card through YooKassa

Worked example: from the "Buy" button to a working engine

Input: you've assembled your own vibe-coding engine on top of Quest and you hit "Buy".

What the engine does (backend):

createOrder in a single transaction: checks that the buyer's org owns the engine (multi-tenant guard), records the referring partner (if any), creates an order with status: pending, creates a payment in YooKassa (idempotency keyed on the order id, redirect confirmation) and stores the payment_url.
You pay by bank card on YooKassa's secure page.
YooKassa sends a webhook. We don't trust the notification body: the status is re-checked with an authoritative request to the YooKassa API (fail-closed — a forged webhook is useless). Processing is idempotent: a repeated notification is simply acknowledged without being processed again; the pending → paid flip is a compare-and-set on the order id and status, so a race between two webhooks can't issue two tokens.
As soon as the payment is confirmed, the system immediately issues your personal install link — nothing has to be activated by hand.
If the order came through a partner, the commission is credited atomically and idempotently (see the article on the partner program).

Result: an install link /install/<token> — a landing page with the package built for your tool (Claude Code / Cursor / AGENTS.md), a README, INSTALL.md and a ready installer prompt.

Installs are counted by seat (a seat-counted license)

Delivery isn't "download once and done" — it's an honestly counted license. The token in the link is a bearer credential, and the machine fingerprint (machineFp) identifies the seat:

POST /:token/materialize {machineFp} — RESERVES a seat (it doesn't count against the limit; the reservation is auto-released after 15 minutes so an abandoned install doesn't burn a slot) and issues a signed download handle.
GET /:token/download?h=... — streams the zip and COUNTS the delivery only AFTER the full transfer (a verified delivery is an ENFORCED counter; an interrupted one doesn't count).
POST /confirm — an HMAC beacon saying "installed/activated". It's ADVISORY: it confirms the fact but NEVER raises the limit and never frees a seat.

How an install seat is counted

1. materialize

reserves a seat, doesn't count against the limit; auto-released after 15 minutes

→

2. download

delivery counts only AFTER the zip is fully sent; an interruption doesn't count

→

3. confirm

an advisory "installed" beacon: doesn't raise the limit and doesn't free a seat

ENFORCED — step 2 only; exceeding the seat limit → 403 INSTALL_LIMIT

Exceeding the seat limit → 403 INSTALL_LIMIT. The install page always checks order.status = 'paid' — nothing is served before payment.

What you buy is yours forever

The package sits on your disk in plain form, works offline and doesn't depend on our servers: the version you bought stays with you. If you request a refund, the install link simply stops working. Question about a payment or a refund? Write to support — we'll sort it out like humans.