Welcome offer: WELCOME30 takes 30% off your first year. It expires on a real date — the code stops working at checkout the moment it does — and your renewal is at list price, which is written on the cards above rather than buried in a confirmation email.
Maistik Forge Kit is a licensed tool, not a subscription to somebody else's cloud. You buy access to the binary and every release for a year — then it runs entirely on your own machines, on your own repositories. Your code and repositories never leave your machine; Forge does send anonymous usage/error telemetry (see Installation for what's collected and how to opt out).
Solo seatsTeamEnterprise
510
1 developer: one Solo seat, $490 a year.
Per developerYour license
Solo
For the independent developer or consultant shipping their own work.
Every license is the same product. The only differences are how many developers it covers and what paperwork comes with it.
The forge binary — a single static Go executable, no runtime, no Node, no network dependency.
Unlimited repositories, unlimited CI — seats count developers, never machines. Runners, hooks, and autonomous loops are free at every tier.
Every agent adapter — 24 dedicated adapters for the AI coding agents you already use, plus a generic one for everything else.
The complete harness — the guardrails gate, verify circuit-breaker, spend budget, secret and PII scan, and the bounded autonomous run. Real gates that return a non-zero exit, not advice.
The full SDD workflow — one canonical spine whose ceremony scales to the size and risk of each change.
A year of releases — every update published during your license term.
Support from the people who wrote it — not a ticket queue.
Doesn't cloning the repository already give me the right to use it?
No. Repository access and a license are two different things. You may read, clone, or fork the source, but running Forge to get its operational benefit requires an active paid license. The license page explains this in plain language, and the LICENSE file governs.
Through private access to the release repository, which is why checkout asks for your GitHub username. One account per seat — add the username of every developer who needs access and they will be added after purchase. That repository carries compiled binaries only, never source.
If you are one person, Solo. If there are several of you, do the arithmetic on the cards above. Under the break-even count, buying individual Solo seats is genuinely cheaper, and we would rather you did that than overpay. From the break-even count up to the Team seat limit, Team is both cheaper and simpler — one invoice, one renewal date, and no per-seat maths inside the license.
Past the seat limit it is Enterprise, and we price it with you.
Do CI runners, hooks, or automation count as seats?
No. Seats count developers, not machines. Run forge on every runner in your pipeline, in every pre-commit hook, and in every autonomous loop you like. Enforcing the harness everywhere is the entire point of it, and charging you per runner would be charging you to use the product properly. Repositories are unlimited for the same reason.
Tell us, and we will move you onto an Enterprise license priced on your real headcount and terms. Access to the release repository is granted per developer, so adding people involves us either way — we would rather it be a short conversation than an awkward one.
Yes. A license covers the developers who run forge, wherever the code lives. Your client does not acquire a license by virtue of you working on their code — if they want to run Forge themselves, they need their own.
No — your code never leaves your machine. Forge has no model of its own and is not a hosted service. It configures agents you already have and runs locally from a single binary. Your specs, timeline, and spend records live on disk under .forge/, where you can read, diff, and commit them. Forge does send anonymous usage and error telemetry (command name, version, OS/arch, a random install ID); set FORGE_NO_TELEMETRY=1 to opt out.
No. There is no license server to time-limit a trial against, and we are not going to build one just to hold your machine hostage for a fortnight.
Everything except running the binary is open to you before you pay. The whole spine — spec, design, tasks, implement, verify — is documented here, and the reference covers every command and every gate. If the workflow is not how you want to work, that is visible long before checkout.
Enterprise buys under a signed order form, where evaluation and cancellation terms are part of the negotiation.
How does the welcome code work, and what do I pay at renewal?
WELCOME30 takes 30% off your first year at checkout — Solo $343 instead of $490, Team $1,715 instead of $2,450. Paste it into the promotion-code box on the Stripe page. It applies to Solo and Team; Enterprise is quoted, so the code does not apply there.
You renew at list price. $490 for Solo, $2,450 for Team. We are telling you that here, before you pay, rather than in the renewal email — the discount is on the first year and we are not going to pretend otherwise.
The countdown is real. The code carries an expiry date at Stripe, and when the timer on this page hits zero the code stops working. It is the same instant for everybody: there is no per-visitor timer that quietly restarts when you open a private window, because a deadline that resets is not a deadline.
If the timer runs out before you have made up your mind, nothing else moves. The list price is the list price, and it was set to be worth paying without a discount attached — a launch code is a reason to decide sooner, not the difference between a good decision and a bad one.
Licenses are billed annually and renew until you cancel. Cancel from the billing portal at any time.
How does activation work? Do I need to be online?
You paste a signed license key into ~/.forge/license — or set FORGE_LICENSE — once. Forge verifies the signature locally, on your machine, with no network call. It works air-gapped, on a plane, and inside a CI runner with no egress.
Before your key expires, Forge warns you on every run for fourteen days, then keeps working through a seven-day grace period after the expiry date, and only then refuses to run. Your pipeline will never go red at three in the morning because a renewal invoice was sitting in somebody's spam folder.
Signed keys are not shipped yet — today your license is your access to the private release repository, and there is nothing to activate. When keys land, the behaviour above is what you will get, and we will not be adding a license server to go with them.
We need something else — a different structure, procurement paperwork, a security review.
That is a conversation, not a checkout button. Book a call and we will sort it out.