Export, GitHub & eject

Own every line

"Own your code" is checkable, not a slogan. From the project menu:

• Export code (.zip) — download the complete project: every page, component, config, and image. It works even when no build sandbox is running, because exports are served from the durable snapshot.
• Push to GitHub — connect your GitHub account once (via a GitHub App that you install on your account — opix gets no access to anything else), and opix creates the repository under your name and pushes the full app.

Both are owner/admin actions in team workspaces.

What's in the box

The export is the app, cleaned for ownership:

• Platform instrumentation (the preview bridge used inside the opix workspace) is stripped.
• Secrets are never included. Instead you get a .env.example naming every variable your app expects — database URL, connector keys — so wiring up your own environment is a checklist, not archaeology.
• A README with real run instructions is added if your app doesn't have one.

Eject without a rewrite

The stack is deliberately boring to leave: standard Next.js (App Router, TypeScript, Tailwind) and standard Postgres. npm install && npm run dev runs it locally; any host that runs Next.js runs it in production. Point DATABASE_URL at your own Postgres and the data layer follows.

There's no proprietary runtime, no opix SDK baked into your business logic, and no export tax. If opix stops earning its keep, leaving is a deployment — we'd rather keep you by being good.