The import doorway
Build anywhere. Prove, launch, and grow with PromptUI.
AI coding tools are great at writing apps and silent about what comes next. Import yours and get the second half: verification on the real rendered app, a live deploy, shareable proof, and a launch you review.
- 1
Push to GitHub, import in one click
Push a standalone Vite or Next.js App Router app to GitHub with its package.json at the repository root. PromptUI checks compatibility before creating a builder session.
- 2
Verify the rendered app
PromptUI runs your app for real and checks the rendered result — the layer users actually meet. Findings come back for your review, and fixes are plain-language prompts.
- 3
Deploy, prove, and launch
One click puts it on a live URL. The checks it passed live on a shareable proof page, and the launch page drafts posts, images, and video about your real app — nothing publishes without your approval.
What the import gets you
Verification on the real render
Not a lint pass — the app is loaded like a browser loads it, and the checks look at what painted.
A live URL with proof attached
Deploy from the same screen, and keep a public proof page recording the checks each build passed.
Your code stays yours
Import reads from your repository; GitHub sync pushes back changes you choose. There is a VS Code extension for editor handoffs too.
A launch that follows the deploy
Launch kit drafts, a findability check on your live app, and a Growth Agent that works review-first.
The review contract holds everywhere: verification findings, deploys, and every marketing draft wait for your approval. Nothing ships or publishes without you.
Common questions
- Which tools can I import from?
- Any tool whose output reaches GitHub: Claude Code, Codex, Cursor, Lovable, Bolt, Replit, v0, or code you wrote yourself. The import reads the repository, not the tool.
- What kinds of apps work best?
- Standalone Vite web apps and Next.js App Router apps at the repository root are supported. CRA/CRACO, Next.js Pages Router and workspace/subfolder selection are not supported. Python and other non-JavaScript backends are not started or deployed by importing the frontend. Services and credentials must be configured separately; preview and deployment still need verification.
- Do I have to rebuild anything?
- For a supported repository, import preserves your existing source and toolchain. Unsupported apps may need a separately reviewed migration; moving files to the root alone does not make an unsupported framework work. Verify the complete app and connected services before publishing.