A Next.js generator that writes code you’d merge.
opix generates complete Next.js applications — App Router, TypeScript, Tailwind, a dedicated Postgres database — from a plain-language prompt. Every build is type-checked and runtime-smoke-tested before you see it, and the repository exports to GitHub whenever you want it.
Free welcome credits · no card required · failed builds cost $0
Generated code should be boring
The test of AI-generated code isn’t whether it runs once in a demo — it’s whether a developer opens the repo six months later and finds it unremarkable. Idiomatic file structure, obvious naming, no clever indirection, no proprietary framework holding the app hostage.
That’s the bar opix generates against: a standard App Router project with server components where they belong, TypeScript throughout, Tailwind for styling, and Postgres behind it. No custom runtime, no magic imports — the kind of codebase you’d get from a careful senior who read the docs.
You can watch it happen. Files stream into the workspace as they’re written; open the code view to read or edit any of them by hand. It’s a generator you can look in the eye.
The gates every build passes
tsc, actually run
Every generation is type-checked in the sandbox. Errors are repaired automatically and re-checked — 94% of first builds compile clean.
Runtime smoke test
Compiling isn’t working. opix loads the preview; on a 500 it reads the dev-server error, finds the suspect files, and fixes them before you ever see the build.
Real version history
Every change is a restorable version. Walk the app’s history, roll back in one click, and export the whole repo to GitHub.
Postgres and auth wired
A dedicated Neon Postgres instance per app with authentication generated in — schema and queries live in the repo, not behind an API you can’t read.
Edit-by-hand friendly
The built-in code view is a real editor. Hand edits and prompted changes coexist — opix works with your modifications, not around them.
Eject without ceremony
Standard Next.js means standard deployment. Take the repo and the database and run them anywhere Node runs.
Prompt to repo
Prompt — or plan first
Describe the app, or use plan mode to review and approve an implementation plan before generation starts.
Generate through the gates
Files stream in; the type-check and runtime gates run; anything that fails is repaired for free before it reaches you.
Own the output
Iterate by prompt or by hand, then export to GitHub — or keep shipping from opix. Either way is reversible.
For developers, honestly
opix won’t replace you; it replaces the empty-repo phase. The scaffold-auth-CRUD-forms week compresses into an afternoon, and you spend your time on the parts that are actually yours — domain logic, integrations, the weird edge cases.
And when a build goes somewhere you wouldn’t, you’re not stuck prompting into the void: open the code, fix it like code, and keep moving. The meter shows what every generation cost, so you can decide when prompting beats typing.
of first builds compile clean through the type-check gate
from prompt to a running dev server with live preview
for failed generations and automatic repairs
Asked before you asked.
What exactly does opix generate?+
A standard Next.js App Router project: TypeScript throughout, Tailwind for styling, server components and route handlers where they belong, and a Neon Postgres database with auth wired in. Dependencies are ordinary npm packages with a lockfile in the repo.
Can I edit the code directly?+
Yes — the workspace includes a code view that’s a real editor. Hand edits are first-class: opix reads the current state of the files before every change, so your modifications and its generations coexist.
Can I import an existing repo?+
Not yet — opix starts projects itself today. You can rebuild an existing app quickly by describing it and pasting screenshots, and export at any point. Bringing your own repo is on the roadmap but we won’t pretend it’s shipped.
Does it write tests?+
The default quality gates are the type-check and the runtime smoke test, run on every build. If you want unit or e2e tests, ask for them in the prompt and they’re generated like any other code.
Is the database really mine?+
Yes — each app gets its own Postgres database, not rows in a shared store. It’s standard Postgres: dump it, move it, point the ejected app at any Postgres host you like.
What does it cost?+
A live meter shows each build’s cost before and after it runs; hard spend caps bound the total; failed builds are free. Plans start at $29/month, and one-time packs from $10 never expire.
Skip the empty repo.
Generate the scaffold you’d have written anyway — then read every line of it. Welcome credits free.