Preview deployed!
Pushed to your GitHub, live on Vercel
2:34 PM
Your GitHub · Your Vercel · Your machine
From Idea To Live Product
A local-first AI product studio that turns notes and references into a real, deployed product you own.
Download for Windows0s
Idea To Live Preview
0%
Code You Own
0
Specialist Agents
0
Local & Cloud Modes
Builds on the stack you already use
GitHub
Vercel
Next.js
Node.js
npm
Ollama
Figma
Docker
The workspace
One Private Workspace
Canvas, chat, code, previews, deployments and project memory in one place — instead of six tools that never talk to each other.
Connect your
own accounts.
You stay the owner of everything
GitHub
Vercel
Ollama
LM Studio
Figma
Aporion plans it.
Builds it. Ships it.
Agents write real code, run the build and open the preview.
48 hours
idea to production
MON
TUE
WED
THU
FRI
SAT
SUN
Ask your project
anything
Core Features
Built To Ship, Not Demo
Everything you need to go
from idea to production
A booking site for a recording studio —
calm and minimal, with
Stripe checkout and a client
dashboard
Turn into a brief
Canvas To Structured Brief
Local & Cloud Models
Everything Traceable
The product
Idea, Code, Deploy
Not a chatbot, a whiteboard or a site generator bolted together — one workspace that carries a project from first note to production.
Canvas
Notes, screenshots, references, requirements, wireframes and task cards on one board — the visible context your agents work from.
Build
Real Next.js, React, TypeScript and Tailwind in a normal repo — generated, edited, linted, type-checked and built.
Preview
The app runs locally while you talk to it. Ask for a change, watch it land, keep or revert it.
Deploy
Branches, commits and pull requests in your GitHub; preview builds in your Vercel. Production is always an explicit yes.
Project Memory
Briefs, decisions, chats, commits, builds and deployments stay linked — so “why is this here?” has an answer months later.
Local AI
Run models on your own machine through Ollama or LM Studio, or mix local and cloud per task. You choose what leaves the device.
How it works
Capture, Build, Ship
The same loop every time — and you approve anything that leaves your machine.
-
Capture
Drop the idea, references, screenshots and notes on the canvas. Aporion turns the mess into a brief, a sitemap and a task list.
-
Build
A real codebase appears in your workspace. It runs locally, you see every diff, and changes happen by asking for them.
-
Ship
Commit to your GitHub, preview on your Vercel, approve production. Then keep iterating in the same workspace.
Real code
No Black Box
Aporion writes an ordinary project you could have written yourself — open it in your editor, hand it to a developer, take it anywhere.
- Next.js, React, TypeScript and Tailwind
- Standard npm, pnpm or Bun project structure
- File diffs shown before anything is applied
- Meaningful commits, .env.example and setup docs
// generated by Aporion · reviewed by you · your repo
import { BookingForm } from "@/components/booking-form";
import { Hero } from "@/components/hero";
export default function Page() {
return (
<main className="min-h-dvh bg-neutral-950">
<Hero title="Book the room" />
<BookingForm checkout="stripe" />
</main>
);
}
The team
Nine Specialists
Not autonomous employees — tool-scoped workflows that run under the permissions you set, and show their work.
Planner
Turns ideas into requirements, scope, milestones and a build plan.
Designer
Turns references and instructions into UI direction, layouts and components.
Builder
Creates and edits the actual codebase, file by file, diff by diff.
Reviewer
Checks consistency, bugs, accessibility and responsiveness before you see it.
Tester
Runs builds, type-checks, linting, tests and browser checks.
Deployer
Prepares commits, GitHub pushes, Vercel previews and approved releases.
Researcher
Collects and summarises web research and documents you approve.
Asset agent
Generates and organises images, brand assets and 3D concept models.
Project manager
Keeps tasks, decisions, blockers and history straight across the project.
Control
Powerful, Predictable
Agents work inside folders you pick, with tools you allow. Anything consequential stops and asks — and every action leaves a record of what it did, why, which files changed and who approved it.
- Run models locally with Ollama or LM Studio
- See which model is active and where data goes
- Preview deploys by default, production by approval
- Stop any browser or command action instantly
- Read project filesSelected folders only
- Create or edit filesShows the diff first
- Run commandsAsks unless trusted
- Push a commitAsks every time
- Preview deploymentAsks the first time
- Production deploymentAlways asks
- Delete files or dataAlways asks
- Browser automationVisible & stoppable
Pricing
Bring Your Own Keys
Local models are free forever. Pay only when you want cloud models, more projects, or people working beside you. Only the Local plan is open today — the paid tiers have no checkout yet.
Local
$0/month
Everything runs on your machine.
- 1 active project
- Ollama and LM Studio models
- Canvas, build, preview and code
- GitHub export
Studio
$39/month
For founders shipping real products.
- Unlimited projects
- Hybrid local + cloud models
- Vercel previews and releases
- Full project memory and history
Agency
Custom
For teams and client work.
- Shared workspaces per client
- Org-wide permission policies
- Private model endpoints
- Onboarding and priority support
Download
Windows, Today
One build exists right now — a 64-bit Windows installer. macOS and Linux are not packaged yet, so there is nothing here to click for them.
Windows · x64
Aporion 2.1.60
An NSIS installer that lets you pick the install folder. It updates itself from the same release feed after that.
Download for WindowsmacOS and Linux builds do not exist yet. When they do they will appear on the releases page.
- Version2.1.60
- Released6 Sep 2026
- InstallerNSIS · 223,592,192 bytes
- Architecturex64 only
- RequiresWindows 10 or later
- Code signingUnsigned
- Update feedgithub.com/0xDI/aporion
- macOS & LinuxNot built
What you will actually see on first launch
This installer is not code-signed. Windows SmartScreen will show “Windows protected your PC” and hide the run button behind More info → Run anyway. That warning is about the missing certificate, not about anything the installer does — and the only thing that removes it is an OV or EV code-signing certificate, which has not been bought. Verify the file yourself before running it if you would rather not take that on faith:
SHA-512 · base64
LDyxPfLPXtw+OhsUskKUoYiHyDDAnF8zYF7ds6QSlsz8VVbLJG8+owQ6eGZ79tlODcAYXDL/uoNqA5ujNnD0xw==
Use Aporion in your browser, connected to your computer
Turn on Settings → Privacy & Security → “Reaching this computer from another device” and Aporion serves its own interface from your machine. Open it in a browser — on that computer, or on a phone or laptop on the same network — and you get the app: projects, plans, canvas, build logs, code, Git history.
The work still happens on your computer. Your files, your Git checkouts, your npm install, your dev server, your keys. The browser is a second screen with a signed identity, not a second copy of Aporion — and every write, build and deploy a browser is allowed to start still opens its approval dialog on the machine, where you answer it.
A device has to be paired before it can do anything. It generates a key the browser cannot export, and you confirm it at the computer. It starts able to watch only, and you promote it there when you want it to act.
Read this part before you plan around it. The promotion only takes effect over a connection Aporion treats as protected, and today that means a browser on the same computer. The listener other devices reach is plain HTTP with no certificate, so Aporion holds every session that did not arrive over loopback at watching only — whatever tier you granted the device. A phone or a second laptop is a live read-only screen: it follows a build, it does not start one. That cap is enforced in the relay, not a setting you can talk it out of, and it stands until these connections are encrypted. Anything a device may not do says so at the button, with the reason, instead of failing after you press it.
This is not a cloud product. Nothing runs on our servers, there is no account to make, and if your computer is asleep the browser tells you that rather than pretending. A hosted Aporion — one that builds and previews your project with no machine of yours involved — does not exist and is not close.
FAQ
Good Questions
Completely. Aporion produces ordinary files in an ordinary Git repository — Next.js, React, TypeScript, Tailwind — in your GitHub account, deployed from your Vercel account. Stop using Aporion tomorrow and the project keeps working.
No. You can work entirely from the canvas, chat and preview — describe what you want, review what changed, approve the deploy. The code workspace is there when you or a developer want it.
Local models through Ollama or LM Studio, cloud models through a provider you connect — Groq, OpenRouter, Gemini and others — or a hybrid where private work stays local and only harder tasks go out. The active model and its destination are always shown.
Read inside the folders you selected, and propose changes as diffs. Running commands, pushing commits, deploying, deleting anything or automating a browser all require approval — production deploys every single time.
Yes — import an existing repository, and Aporion reads the codebase, explains the architecture, works on a branch and opens a pull request you review like any other.
No, and there is no plan to pretend otherwise. What does exist is browser access to your own machine: install Aporion, turn on remote access in Settings, and pair the browser. On that same computer the browser gets the full app. A phone or a second laptop on the same network gets a read-only view of it — that connection is plain HTTP with no certificate, so Aporion holds it at watching only until these sessions are encrypted. A genuinely hosted Aporion would need to run builds and previews on someone else's servers, which is an isolation and funding problem we have not solved. Until it is solved, this page will not claim it.
One outcome done properly: an idea and its references become a polished Next.js site you review locally, export to GitHub and deploy to Vercel. Mobile apps, computer use, deeper 3D and messaging integrations come after that loop earns its keep.
Get started
Start With An Idea
Bring a rough one. Aporion will shape it, build it, show it to you running, and put it live in accounts you already own.
Local-first · Your GitHub and Vercel · Free with local models