The Putnami tooling and frameworks are public since 0.2.0, on 2026-10-01. PR validation, the factory setup, and the design partner program are available today. Intelligence and Cloud remain private until the support, distribution, and operational evidence justify a broader promise.
The release view says what can be used now without manufacturing a launch date or a cadence.
Available now
Begin with the problem your team already has.
The first engagement does not require source availability, self-service onboarding, or adoption of the Putnami stack. It begins with evidence from one representative system or change.
Available now
PR validation
A computed verdict on each pull request, in your own GitHub Actions. $48 per seat per month, with a 7-day free trial.
Available now
Set up your factory
Four weeks to get a verdict on every pull request of your repository, set up with you. €9,900 excl. VAT.
Available now
Design partner program
A private channel with the founder and a weekly call, for 3 or 6 months.
The tooling and frameworks are public: the source is on GitHub and the docs are on putnami.dev. Intelligence and Cloud remain private, and private product work is not presented as generally available.
Public · 0.2.0
Putnami Tooling & Frameworks
Supported Go and TypeScript surfaces, deterministic jobs, impact analysis, and local or CI operation. Public on GitHub since 2026-10-01, with the docs on putnami.dev.
Private beta
Putnami Intelligence
Default-branch indexing, structural reads, MCP access, and pull-request intelligence are being validated on real repositories.
Managed development
Putnami Cloud
Identity, configuration, source, distribution, and control capabilities exist; the complete managed lifecycle remains product direction.
The license is FSL-1.1-MIT (Fair Source). You can use Putnami for any purpose, including commercial production, except to offer a commercial product that competes with it. Each release becomes MIT two years after its publication. We intend to publish 1.0 under MIT. Read the docs on putnami.dev
Release principle
Open capabilities when the evidence supports the promise.
No announced launch date or committed cadence.
Presence in a repository does not imply public availability or support.
Each status states what a user can rely on today and where the boundary remains.
Access expands capability by capability, with no requirement to migrate the full stack.
Start from the client problem, agree the time and commercial boundary, inspect a real change, and decide explicitly whether to stop, extend the mission, or continue as a design partnership.
Select one recent change or delivery path with representative friction.
Agree access, confidentiality, time, budget, and payment before substantial delivery.
Use Putnami capabilities only where they produce credible evidence for the client problem.
Separate client-specific work from reusable product learning at the continuation checkpoint.