Trust infrastructure for software change

Don't judge the change. Compute it.

On every pull request, Putnami computes a verdict from what your system declares it must do: what the change reaches, what is proven, and what is still missing.

See real verdicts See pricing See how Putnami works

Start with the system you have.Integrate first. Migrate only when the evidence earns it.

The problem

More code is being produced. Understanding is not scaling with it.

Every meaningful change asks a team to reconstruct what the system is, what must remain true, and what the available checks actually prove. Agents increase change volume without increasing reviewer capacity at the same rate.

Intent: Lives across tickets, documents, decisions, and the people who still remember why.
Impact: Is reconstructed from repositories, ownership boundaries, dependencies, and experience.
Evidence: Is fragmented across tests, CI, artifacts, environments, and runtime behavior.
Coordination: Fills the gaps through review queues, handoffs, repeated explanations, and late corrections.

The change record

A change should carry its own explanation.

Putnami makes the change the shared object between people, agents, repositories, delivery systems, and environments. Each claim stays connected to the revision and evidence that support it.

Intent
Indexed revision
Affected system
Constraints & decisions
Checks & evidence
Observed outcome

Not another document to keep synchronized: one versioned intention, with facts and evidence derived from the systems that already own them.

Progressive adoption

Integrate first. Migrate only when Putnami has earned it with evidence.

Receive useful, portable information from the system you already run. Adopt one additional Putnami capability only when it removes a demonstrated constraint.

Connect: Discover an existing repository and normalize its operations without changing its stack.
Understand: Expose revision-specific structure, ownership, dependencies, specifications, constraints, and impact.
Verify: Connect checks and evidence to the exact claims and change they support; show what is missing or stale.
Operate: Adopt managed delivery, runtime, observability, and recovery only where stronger guarantees are useful.

A team may remain permanently on a partial integration. Full framework or Cloud adoption is not the ticket of entry.

One Putnami

Open foundations. Shared intelligence. Managed guarantees.

These are progressive depths of one product promise—not separate stories a team must understand before it can begin.

Public · Fair Source

Contract, Tooling & Frameworks

Portable contracts, local tooling, and native Go and TypeScript implementations make the system legible and executable without a Cloud account. The source is public on GitHub.

Private beta

Putnami Intelligence

Revision-specific repository understanding, impact, evidence, MCP tools, and pull-request checks shared across teams and agents.

Managed expansion

Putnami Cloud

Managed artifacts, delivery, environments, runtime, observability, policy, and recovery progressively close the operational lifecycle.

For developers

The system is public. Run it on your machine.

The Putnami CLI and the Go and TypeScript frameworks are on GitHub under FSL-1.1-MIT. The docs live on putnami.dev.

macOS · Linuxcurl -fsSL https://putnami.dev/install.sh | bash

Windowsirm https://putnami.dev/install.ps1 | iex

Getting started

Install the CLI, create a project, and run the full system locally.

Read the guide

Develop with AI assistants

Claude Code, Codex, Cursor, or Copilot work from the same workspace facts and commands.

Set up your assistant

Source on GitHub

Read the code, follow the releases, and report a bug in the supported core.

Open Putnami/putnami

Read the docs View on GitHub

Current truth

What exists today, and what remains product direction.

Repository presence, an accepted design, and a supported release are three different facts.

Public · Fair Source

Supported core

CLI, Go and TypeScript surfaces, deterministic jobs, impact selection, and local or CI operation. Public since 0.2.0, under FSL-1.1-MIT.

Read the source on GitHub

Experimental

Executable intent

Python support, SDD, and ARC/DARC remain explicit experiments while their value is measured.

Private beta

Intelligence

Default-branch snapshots, structural reads, MCP access, and pull-request intelligence.

Product direction

Operable lifecycle

A complete causal chain from intent and source change through delivery, runtime, and recovery.

Evidence before claims

The reasoning, experiments, and limits are written down.

Putnami is being tested on real repositories, release paths, and high-volume agent work. The research surface keeps the conclusions inspectable and the unanswered questions visible.

Explore the research Work with Putnami

For clients and design partners

Become a client. Become a design partner when the fit is real.

Bring one software change your team finds slow, risky, or difficult to explain. Start with a bounded client engagement, then shape Putnami around the constraint only when that creates value for both sides.

Your email is used only to start this conversation—never a release waitlist.

See how working together begins →