Best to sell code.
The algorithm you perfected. The model that solves a hard problem. Turn your expertise into a product customers can run on their own infrastructure—even offline.
A signed right to run your product, carried into the customer’s deployment. The plan brings offers, acquisition, local execution rights, and developer payout records into one workflow—so you can focus on the capability worth buying.
Planned for V1
Two starting points, with the covered releases, deployment scope, and terms made clear before purchase.
Offer ongoing use of identified product releases. A natural fit for a reusable library, a specialist model, or a component that becomes part of someone else’s application.
The planned experienceVerify the grant at admission, then run within its agreed scope. Unlimited grants need no ongoing usage meter.
Offer a defined quantity of completed work at a supported result boundary. V1 starts with one unit per durably committed operation, such as an accepted report.
An illustrative offerTen committed reports. Recalculating a preview or retrieving the result of the same completed operation adds no new charge.
The proposed experience
A customer should be able to discover your product, understand the offer, acquire the rights, and put it to work. Grid’s plan connects the commercial agreement to the exact code being run.
Identify the release, included rights, supported deployment, and what counts as a unit of work.
The purchase authorizes one grant, delivered over the network or through carried files for an isolated environment.
The deployment verifies its rights and uses the capacity it holds. Reconcile records and import purchased refills later.
These are proposed V1 capabilities for Grid 0.70.0. Execution Grants are not yet available to purchase or activate.
Designed for the way developers build
The V1 plan lets a provisioned deployment operate within purchased capacity without a vendor heartbeat or calendar expiry on that capacity. Signed grant and refill files can cross an air gap through an approved transfer process.
Count a committed result under the offer’s declared meter. Keep the price of that result stable as Grid optimizes, caches, or recalculates the model behind it.
V1 proposes fixed, agreed revenue shares for named collaborators and authorized bundled dependencies. Give the buyer one offer with the included rights resolved together.
The design keeps commerce out of the evaluator. Ordinary code should carry no commercial work; metered products account at the selected operation and durable result boundaries. V1 assigns each finite allocation to one active capacity owner. Shared fleet pools and stronger hardware-backed protection belong to later stages.
Start today
Turn your knowledge into a model. Package it for reuse. Learn the existing publishing flow for signed packages, templates, and Domain Packs in grid ns while Execution Grants take shape.