Lovable, v0 and Cursor are very good at generating code, and we won't tell you otherwise. The difference is what you're left with when the process ends.
What you get
Form leads
Your business data
Publishing
Who maintains it after
Coding required
A SaaS app with its own users
That last row is on purpose: if your project needs its own users, payments through your merchant account, or logic where a silent error breaks the business, XIA Coder tells you upfront and we hand it to the team. We'd rather declare a ceiling than run a failed demo.
There's no project to configure, no repository to clone, and no environment variables to paste.
Type /site and tell it what the business is, what you want to show and with which data. If something's missing, it asks before writing a line.
The site compiles and you see exactly how it will look, on desktop and mobile, before it exists on the internet. You ask for changes in the same chat.
One button. It goes live on your subdomain with a valid certificate. If you have your own domain, the agent walks you through connecting it.
/site landing page for Talleres Rivadavia, engine machining in
Mendoza since 1978. Services, WhatsApp contact and pricing from
the "List 2026" sheet.This is what no website builder can give you: the primitives already exist in your account, so the site needs no backend of its own.
The site's form is a Napsix Form. Every inquiry lands in your pipeline with its contact, ready for an agent to work.
If your team keeps the list in a XIA Sheet, the site shows it. You update the sheet and never touch the site.
Photos already in NapsixStorage are used directly, with no re-uploading somewhere else.
The embeddable chat answers from your Knowledge Base, so visitors get the real answer from the business.
In another builder
A form needs a backend, a database, an email provider and the wiring between all four. Each one is a separate project.
Here
The form already routes to your CRM. There's nothing to wire because the pieces were already yours.
Create the site inside a Project and it keeps its tasks, its chat and its artifacts. The team sees where it stands without asking.
Sites belong to the team, not to one person
A published site is already public on the internet, so hiding it from a teammate protects nothing — it only stops someone from fixing it. The list groups them into "Mine" and "Team", with the name of whoever created it.
What's left before publishing becomes an assignable task, not a message lost in a chat.
The site, documents, sheets and dashboards of the same project, in a single tab.
The conversation where it was born is the record of why each decision was made.
Anyone on the team opens the site and continues. It doesn't depend on who started it.
You're live on day one without buying anything. When the site becomes the face of your business, you move it to your domain.
yourbusiness.napsix.one
yourbusiness.com
If you already own the domain, the agent tells you which record to add and where, and confirms when it propagated. If you don't have one yet, it helps you pick and register it from the platform.
Documents, sheets and dashboards face inward. The site is the same information, facing out.
Proposals, contracts and reports the agent writes with your data.
Collaborative sheets. They're the source of the site's prices and catalog.
Live KPIs and charts over that same data.
The public site. The only Canvas surface your end customer sees.
No card to start. These are the limits the product actually enforces, not a marketing list.
| Free | Starter | Pro | Business | |
|---|---|---|---|---|
| Published sites | 1 | 3 | 10 | 50 |
| Napsix subdomain with TLS | ||||
| Your own domain | — | — | ||
| Version history | 5 | 20 | 100 | 500 |
| Share the preview before publishing | — |
No, and we'd rather tell you before you try. XIA Coder builds sites and microsites wired to your operation. If your project needs its own users isolated from each other, payments through your merchant account, or logic where a silent error breaks the business (bookings with capacity, committed stock), the agent says so in the chat and we hand it to the team as a project.
No. You tell it what the business is and what you want to show, in your own words. The agent writes the code, compiles it and shows you the result before publishing. If you don't like something, you ask in the chat.
No. Each conversation has exactly one site: if you ask for a change, it edits the existing one and keeps the previous version in history. That's enforced in the product, not just requested in the instructions.
Yes. The agent creates a real Napsix Form and passes its identifier to the site, so every submission lands in your CRM with its contact. It's not a mailto or a decorative form.
Yes, from the Pro plan. The agent gives you the exact DNS records, verifies they're right and confirms when it propagated. If you don't have a domain yet, it helps you pick and register one from the platform.
Yes. The agent writes CSS animations: transitions, fade-in on load, hover, moving gradients. If you ask for something your plan can't do, it says so in the chat instead of shipping it broken.
From your NapsixStorage, or URLs you give it. The agent doesn't invent photos of your business: if it has no real images, it asks for them or leaves the space ready for when you upload them.
Sites beyond the free plan's limit stop being published, but they're not deleted: the code and history stay in your account and you can publish them again whenever you want.
Works with the rest of your operation
Start free with your first site. No card, no deploy, and no waiting for a developer to free up.
