Your branch is already an environment.
Putnami makes it the system.
Local-first, branch-native tooling designed for humans and AI agents. One structure from laptop to preview to production.
putnami — zsh
Modern stacks are stitched, not designed.
Local, CI, preview, prod are different worlds
Different configs, different behaviors, different surprises. Alignment becomes a full-time job.Branches are just metadata
You already express intent in Git. But environments don’t follow, so review and iteration stay slow.Tooling sprawl breaks predictability
Five tools, three config dialects, and no single system. Small drift becomes operational debt.AI agents can’t reason about your project
If structure is implicit and config is ambiguous, agents guess. Guessing is how they break things.One system, three layers.
1
Workspace
One root, one structure. Multiple projects share tools and code. This is what humans trust and AI reads.2
Framework
Minimal primitives for HTTP, React SSR, SQL, and DI. Opinionated so behavior stays predictable.3
Platform
Operate at scale. Preview environments per branch, deployment pipelines, observability built-in. Zero lock-in.A branch is not just code. It is a runnable environment.
Branch-based previews
Create a branch and you get a preview environment. Same structure, same commands, no extra glue.URLs per branch
Each branch maps to an addressable URL. Review changes in context, not in screenshots.No config drift
Stop maintaining parallel worlds. Local, preview, and production follow the same system boundaries.Fast iteration loops
Small changes stay small. Environments follow Git, so feedback cycles stay tight.Designed so AI can actually work with your codebase.
AI-readable structure
Conventions over configuration. Stable layout and explicit defaults so agents navigate without guessing.Small config surface
Less magic means fewer surprises. The CLI is the interface. The repo is the contract.Works with your tools
Claude, Cursor, and Copilot operate better when the project is predictable. Putnami enforces that.Human and agent parity
Same commands and same workflow. No hidden paths that only “the senior” knows.Built for real repos.
Multi-project by default
Share code between apps without publishing. The CLI detects changes and rebuilds only what changed.Local-first, platform-optional
Full workflow without cloud dependencies. Use the platform only when you want previews and deploys.Constraints we refuse to violate.
Dependencies are liabilities. Every dependency must be justified.
If tuning is required, the abstraction failed. Defaults should handle performance.
Local development must be complete. No cloud-required workflows.
Defaults must be explicit. Avoid ambiguous configuration.
Start with a workspace.
Grow into a platform only when it is justified.