01
Describe it in your own words
You work in your own account. Builds use credits — a free daily grant to start, no card required. Packs are optional when you need more.
Kelvane
Your old legacy app,
turned into an agentic-ready
modern app with built-in MCP.
Same rules. Same business logic. Just modern and better — secure by default, with observability and an audit trail your ops can actually trust.
- Modern stack
- Secure seams
- Observability
- Agentic-ready
- Built-in MCP
warehouse sample · before → after · same totals
Before · legacy order form
Process Order
Customer ID: 4471
SKU: WH-220
Qty: 520
Place OrderNo API · no audit trail · rules only in source
HarborDock
LiveOrder desk · modern stack
Agentic · MCP
New order
Customer
4471
Contract rate
SKU
WH-220
Warehouse
Qty
520
Bulk tier
Pricing rules · audited
- Bulk discount 12%Qty ≥ 500 · audited
- Customer exception +5%4471 · traced
- Freight carrier gap +2%Lane WH-220
Total · matches legacy
$15,136.32
02
Files, store, preview
It writes a real app — routes, records, and a place for your data — then compiles it. What you preview is that build. Not a screenshot generator.
03
It has to run
Preview is live on Kelvane. Production can stay with us, move to your cloud, or ride an edge we stand up together. Hosting is not the product definition.
The moat
UI builders stop at the pixel. This has to run.
First paint is an application: landing, a primary flow, seeded records, and a store. Auth, mail, API, and billing are seams in the kit so the same app can run on Kelvane, on your cloud, or on an edge we operate with you. Zip export exists; it is not the only door.
App
Kit routes, copy, a primary flow, admin/auth files waiting to be switched on.
Data
CSV seed, in-app records, persist to store.json — Postgres when you wire the seam.
Edge
Preview on Kelvane. Production hosting is a choice: stay, move to your cloud, or a written edge engagement — not “you must take a zip.”
Legacy
Contained systems: map the source, modern preview for one workflow; cutover and hosting are quoted.
Two products
Two products. They never share an agent loop.
New app
A new app from a description
Describe the product. Attach screenshots, seed data or a short spec if you have them — everything is scanned before the model sees it. You get the right first screen for that product, filled with your own content, plus one workflow that works. Sign-in, admin, email and payments are wired as seams, not silent production.
- Credits to build · free daily grant · no card to start
- Follow-up changes on the same workspace
- Live preview once it compiles
Existing system
Read the code, then rebuild the screen
Upload a clean source zip. We map it in an isolated sandbox, surface rules nobody documented, ask you about the ones that need a decision, and build a modern screen for one real workflow — with mapped rules cited back to the file and line they came from.
- Mapping and questions are free; builds use credits
- Upload is scanned into an isolated sandbox — never put into the generated app
- Quoted for cutover, hosting, or an ERP core
What first paint includes
- A real workspace in your account that survives refresh
- The right first screen for the product, and one workflow that works
- Live preview of the compiled app, shareable as that preview
- Follow-ups that edit real files
What it does not
- Unlimited model calls — each build is turn- and spend-capped
- PCI, a HIPAA BAA, or treating preview as that by default
- Executing your wrap zip on the Next.js host
- Training a Kelvane model on your briefs — jobs still go to Anthropic to fill or map
Pricing
Credits to build. Quote to go live.
10 free credits each UTC day (up to 40 free per month; unused daily credits do not roll). First build uses 10; follow-ups use 3. Packs from $10 at $0.20 per credit. You get a live preview in your workspace — not production hosting. Cutover, hosting, or an ERP core is scoped and quoted with a human.
Build with credits
10 free credits/day · up to 40/month · no card to start
First build 10 · follow-up 3 · packs from $10 at $0.20/credit
- Map a clean source zip and surface rules we find in the code
- Questions grounded in that map, not a generic checklist
- A first build with a live preview you can click
- Follow-ups on the same workspace (credits apply)
Quoted cutover & hosting
$3k–$12k indicative founding range · timeline scoped per engagement
- Cutover to production and data migration
- Hosting on your cloud, or a written hosting engagement
- ERP or accounting cores that cannot self-serve
Questions
- Is this another unlimited AI app builder?
- No. It starts from screens we designed rather than inventing a layout from scratch each time, and it builds one product properly instead of a demo of everything. It is not ChatGPT with a deploy button.
- Is this just a generated UI?
- No. What you get is a running app: real routes, a working primary flow, records you can search and filter, and a place where saving data plugs in. Sign-in, email, API, and payments are wired as seams — present and ready to connect, not silently pretending to be production.
- What does it cost?
- You get 10 free credits a day (up to 40/month; unused daily credits do not roll). A first build uses 10 credits; a follow-up uses 3. Packs start at $10 for 50 credits ($0.20 per credit) — not a subscription. Cutover, hosting, or an ERP core is quoted with a human ($3k–$12k indicative founding range · timeline scoped per engagement).
- What is a first build?
- A real app you can click, in your own workspace, with a live preview once it compiles. For an existing system, it opens on the work your team actually does, with statuses and numbers from the brief, and mapped rules cited back to the file and line where we found them.
- Can you put our PHP on Vercel?
- Not as a one-click rewrite of the core. After NDA we map a clean PHP zip, ask questions grounded in that map, and build a modern screen for one real flow that you can click. A quote ($3k–$12k indicative founding range · timeline scoped per engagement) covers cutover, hosting, or an ERP core that cannot self-serve — it is not the only way to get a modern UI.
- When do you need an NDA?
- Only for existing-system (wrap) source: zips, SQL, screenshots of today’s UI. New-app builds do not wait on an NDA. The in-product NDA is a click-through gate before we accept that source — not a negotiated MSA, and not a substitute for your counsel.
- What may I attach?
- New app, no NDA: images (png/jpg/webp), CSV/TSV seed data, and short specs (pdf/txt/md), size-capped and scanned before the model sees them. Existing system, after NDA: zip or SQL plus images. We reject executables, HTML/SVG, macros, and passworded archives. Uploads go through intent + scan; dirty files never become clean copies and are not sent to the model.
- Who hosts the running app?
- Kelvane already hosts the workspace preview. That preview is not, by default, a production SLA or a place for live card data or PHI. Production can stay on Kelvane, move to your cloud, or be a written hosting engagement. Export exists so you are not trapped. It is not the only path, and “you host” is not the product.
- Do you train on my briefs or source?
- We do not use your sessions to train a Kelvane model. Build and wrap jobs send prompts and allowed file snippets to Anthropic so the agent can fill or map. We do not send wrap zips until they scan clean. Do not put secrets in briefs if a hash or redaction will do. Anthropic’s terms also apply to that processing.
- Is the generated app production-ready?
- It is a working first paint in a kit: routes, copy, a primary flow, local persistence stubs. Generated auth is a localStorage stand-in until you wire a real provider. Generated billing throws until you connect Stripe. Treat preview as a draft you own, not a compliance certificate.
- Harbor, Lumen, Atlas, Ledger — is that what I get?
- No. Those were static teaser skins. What you get is a real workspace in your own account — including Existing system after a live map. Not a questionnaire mock, and not a reskin of the old pages.
- What are the job limits?
- Each build is bounded: a turn limit and a per-job spend cap, so a run cannot spiral. Mapping an existing system parses the code locally and then makes two bounded model calls (the report and the questions). Account usage is credit-metered — 10 free credits/day, capped at 40/month.
- Cookies and analytics?
- Auth0 session cookies are required to log in. Optional analytics (Plausible) load only if you accept and only if we have configured a domain. Rejecting analytics does not block builds or login. Details are in Privacy.