SaaS booking app
From zero to deploy — patterns, stack and a controlled roadmap through to production.
◆ Who it's for
What's your scenario?
Indie Hacker
You develop solo and need a full team.
Orchestrate agents with defined roles and move at squad speed. Hit your credit limit? Switch tools and continue where you left off.
Tech Lead
The team uses AI, but every dev ships differently.
One workflow, code generated from the Spec. The methodology standardizes delivery, not the prompt.
Startup Dev
Tight deadline. Code that needs to scale.
Discovery, spec and code in the same flow. Review before merge, zero surprises in production.
Polyrepo Team
Your product lives across several repositories.
Frontend, API and services in separate repos, and a feature that has to cross all of them. Workspace mode coordinates everything from a single session.
◆ How it works
Spec-Driven Development in an agents pipeline.
◆ Harness
The artifact that governs everything.
A living artifact, versioned in the repository, encapsulating execution rules.
Boundary
What is in and out of scope. Which modules can be touched, which data is accessible. The agent receives this as a constraint.
Contract
Expected inputs and outputs, mapped edge cases. The harness guides spec generation aligned with contracts without human intervention. In a Workspace, the Contract is the seam between services — every repository reads the same contract and converges on it.
Guardrail
Business rules, performance limits, architectural patterns. Documented during onboarding of an existing application, and as features are generated.
Acceptance
Acceptance criteria defined before any code exists. TDD implementation by default.
Repository-generated documentation
When creating a project, starting a feature, or working in an existing codebase, N45.ai generates and maintains versioned documentation in the repository — the living context that guides every agent.
Documentation
Project
Project identity: type, description, and high-level scope. Created during onboarding and evolved with the product.
Patterns
Architectural conventions, code patterns, observability, and testing. Guardrails every agent respects.
Stack
Technical map: languages, frameworks, dependencies, and layers (frontend, backend, infra).
Runbook
How to install, run, test, and validate health. Commands, ports, and local URLs.
Changelog
Delivery history by feature and fix, updated on every merge.
Tech Debt
Technical debt identified during discovery and execution, with status and traceability.
Diagrams
Architecture Diagram
Structural view: components, layers, and how they connect.
Flow Diagram
Process flows and interactions between parts of the system.
Context Diagram
C4 context view: actors, external systems, and project boundaries.
◆ Workspace mode
One feature. Several services. One orchestration.
Workspace mode coordinates the change across several services — a feature crosses the frontend, the API and whatever else it needs, planned and executed from a single session.
Members
Each repository joins the workspace as a member. They stay independent git repositories; the workspace only coordinates.
Fan-out
Each member gets its own self-contained roadmap, honoring its slice of the CONTRACT.
Parallel execution
Each member moves at its own pace, with no lockstep between repositories.
Unified validation
The services come up together to see the seam working end to end. Then merge or coordinated PR — per member and in the workspace, always your call.
The same pipeline, now across your services.
◆ Agents10 agents
A squad of agents, not a prompt.
Generic AI becomes an engineering squad: each agent has a defined role, isolated context and traceable responsibilities.
◆ Dashboard
Watch your squad's work happen in real time.
A dashboard with your features on a kanban, agents running task by task, quality and delivery metrics, and every project artifact — no log reading required.
Feature progress29%
BACKLOG3
WIP2
REVIEW0
DONE2
Live kanban
The feature's tasks move from BACKLOG to DONE as agents execute them. You see which agent is on which task, right now.
Metrics that matter
Issues found, blocked tasks, degree of parallelism and the feature's burndown — plus a retrospective with recommendations at the end of delivery.
The project's context at hand
Discovery, spec, roadmap and architecture documents open in the browser, on the same screen where the build is happening.
Runs 100% local
The dashboard server starts from your own machine and reads the files of your own repository. None of your code leaves it.
◆ GovernanceEnterprise
Your standards, applied to every execution.
On the Enterprise plan, the organization owner defines the architecture standards and security policies. These are rigid guardrails, applied to every project, every workspace, and every member — without depending on anyone remembering to ask.
Guardrail
Standard and quality guaranteed on every execution. The organization's architecture standards and security policies enter every discovery and every spec.
Automatic adaptation
When a request contradicts a standard, N45 rewrites the plan to the required standard and reports what was adjusted — instead of just flagging it and moving on.
Versioning
Every change to the guardrails creates a new version, with a record of who changed it and when.
◆ SDD vs Vibe coding
Vibe coding doesn't scale.
You describe an idea, AI generates code, you test, tweak, change the prompt, paste pieces together, initial patterns are forgotten, quality drops drastically — you persist until it works.
◆ SUCCESS RATE × SCALE
N45.AI × Vibe Coding
Vibe coding nails the MVP and collapses as the project grows — the entropy breaking point. N45.AI keeps the success rate steady at any scale.
N45.AI
Vibe Coding
How to useGo to documentation →
Get started in 5 minutes:
Compatible with Windows, Linux and Mac. Get running quickly via npx.
Prerequisites
Node 22+GitN45.AIClaude Code / Cursor / Codex
Project
A single repository: one app, one microservice, one monorepo. One session, one repo.
1
Authenticate machine
npx n45-ai@latest login2
Create the project directory
mkdir meu-projeto3
In the project directory
npx n45-ai@latest initSelect your tool and Project mode (one repository)
4
Run in the AI prompt
/n45Workspace
Multiple repositories, polyrepo. A feature crosses the services, coordinated by a shared contract, planned and executed in a single session.
1
Authenticate machine
npx n45-ai@latest login2
Create the workspace directory
mkdir meu-workspace3
Clone the services into that directory
git clone <url-do-serviço>4
In the folder that contains your repositories
npx n45-ai@latest initSelect your tool and Workspace mode — init detects the git repositories in the folder
5
Run in the AI prompt
/n45Documentation
All the commands, the Project and Workspace guides, and the full reference.
◆ Integrations
Runs with your tools.
N45.AI orchestrates on top of what you already use. No lock-in, no stack migration.
Claude Code
by Anthropic
● AvailableCursor
by Anysphere
● AvailableCodex
by OpenAI
● Available◆ NO LOCK-IN
Switch tools without losing context.
Hit your credit limit on Claude Code? Switch to Cursor and continue exactly where you stopped. No handoff, no context transfer: your state lives in the repository.
◇ 7 days free on PRO · cancel with no charge · new subscribers only◇ Install via npx · get started in minutes
Use casesNew app
The same pipeline. Five real contexts.
Discovery, Spec, Code, Review and Deploy — from zero to production, with validation at every phase.
Between each phase, you validate progress before moving forward.
◆ Contact
Ready to get started?
Talk to us and schedule a demo of how N45.AI can accelerate your team.
Information
✉
CORPORATE EMAILinfo@n45.tech
◎
PHONE / WHATSAPP+55 11 97105-9034
◈
LOCATION
São Paulo, SP — Brazil
◆ Real questions
Get your questions answered before subscribing.
Direct is vibe coding — you send a prompt, get code, and quality drops as the project grows. N45.AI adds Spec-Driven Development: Discovery, Spec, Roadmap, parallel agents, automatic review and persistent state in the repository.
Yes. N45.AI orchestrates the workflow within the tool you already use. You need an active N45.AI subscription and at least one of Claude Code, Cursor or Codex.
Yes. The Architect onboards existing code — detects stack, patterns and architecture — before any implementation. Brownfield, monorepos and microservices included.
No. You describe what you want in natural language. N45.AI talks with you, asks what's needed and orchestrates the execution.
Automatic Code Review pipeline at every phase. The Architect validates diffs and acceptance criteria before advancing. You can intervene, pause or cancel at any time.
Yes. State lives in files in the repository. Close the tool, come back days later — resumes exactly where it left off.
7 days free on the full Pro plan. Card required at signup. Cancel before the end and nothing is charged. Billing details on the pricing page.
Yes. The DevOps Agent provisions infrastructure as code — Terraform, Pulumi, AWS CDK. Your production environment is born from the spec, not manual configuration.
The workflow — Spec, Roadmap, tasks — lives versioned in your repository. Code generation uses the AI you chose, with the same privacy rules as that tool.
No. .n45/ files, specs and roadmaps stay in the repo. You lose access to agent orchestration, but the engineering history stays with you.
Yes. If you hit your credit limit on Claude Code, switch to Cursor or Codex and continue where you left off. No handoff or context transfer needed: the project state lives versioned in the repository, so any tool resumes from the same point.
Yes. Workspace mode registers each repository as a member and coordinates the feature across them: a shared CONTRACT, a self-contained roadmap per member and unified validation at the end.
Through the CONTRACT: endpoints, events and schemas with each side's obligations. Each member implements its slice and, in the unified validation, the services come up together to check the seam end to end.
It starts from your own machine with one command and reads the files of the repository you're working on. None of your code, your plan or your metrics is sent anywhere.
On the Enterprise plan, the organization's Owner defines the architecture standards and security policies. They then apply to every planning step done under that organization.
In most cases N45 adapts: it rewrites the plan to the required standard and reports what was adjusted. When the request is irreconcilable with the policy, planning stops and returns the reason, instead of proceeding outside the standard.
Yes. Every change creates a new version of the guardrail set, with a record of who changed it and when.
Build real systems,
not throwaway prototypes.
◇ 7 days free on PRO · cancel with no charge · new subscribers only◇ Install via npx · get started in minutes
Devs who stopped prompting.
“I switched from manual prompting to N45 and stopped reviewing buggy code the AI got wrong. The spec guarantees what gets delivered.”
“I was tired of asking for a feature and watching the AI break something I never asked it to touch. N45 reads the codebase, writes a spec, and executes strictly within scope. It doesn't touch what wasn't agreed on.”
“Our pain was 5 devs, 5 different styles coming out of Cursor. N45 read our codebase, generated PATTERNS, and now any agent respects the project's convention — not whichever dev is at the keyboard.”