01 · What owning it means
Six things that are true of every site you export.
Ownership is not a feeling about a vendor. It is a list of things you can do without asking anyone — so here is the list, written with enough detail to be checked rather than enough warmth to be believed.
- 01The deliverable is a folder, not an account.
A coffee shop with online ordering exports as 180 files; a portfolio with nothing to store exports as 99. You get app/, components/, lib/ and public/, a package.json, and a README written for whoever inherits the site rather than for you — plus prisma/ and server/ only if the site actually stores something. Nothing in the folder is a link back to a dashboard.
- 02The files are ordinary.
Next.js, React, Tailwind and Prisma: the stack any developer you hire next year has already used. There is not one Naratake package in package.json, so there is nothing of ours left to install, license or keep up to date. Run npm install, then npm run build, and it builds.
- 03It runs wherever Node runs.
Push it to GitHub and import it into Vercel, or copy it onto a cheap VPS — the export ships a Dockerfile, a docker-compose.yml, a deploy.sh and a Caddyfile.example that gets you HTTPS on its own. A site with nothing to store needs no database at all. A site that takes orders runs on SQLite while you work and Postgres in production, one line of prisma/schema.prisma apart.
- 04Nothing in it calls us.
Search a whole export for our name and you find code comments and a footer credit line. No endpoint, no licence check, no heartbeat. The only outbound calls a generated site makes are to providers you configured yourself, and the analytics tags emit nothing at all until you paste in your own ID. The AI assistant stays on the editor side of that line: words you accepted from it are ordinary content in the folder, while your provider key and every call to a model stay out of the export entirely. There is exactly one opt-in exception, and it is named in the next section rather than left for you to find.
- 05A lapsed licence cannot reach a site you already shipped.
Stop paying for the desktop app and the editor keeps working with every project untouched; what pauses is the pair of shipping actions, export and deploy. A site already sitting on your host — or your client’s — never contained a line of code that asked us for permission, so there is nothing left for us to withdraw.
- 06The money never passes through us.
A published site charges cards with your own Stripe secret and publishable keys, into your own Stripe account. We take no percentage because there is no moment at which we are holding the money. The other side of that arrangement is simple: you paste your own publishable and secret keys once at setup, and from then on every payment settles in your account with no Naratake balance in between.
02 · Where the guarantee stops
The sentences that would turn this page into a lie.
Each of these is something you would rather read here than discover at the finish line. They are also the reason to believe the six above.
And one that is easy to miss: a starting point arrives with demonstration photographs, and in the exported folder those are still addresses at the stock library they came from. Swap in the client’s own pictures before you call the folder finished — nothing you deliver should be resting on a placeholder.
03 · Check it yourself
Do not take our word for any of it. Five minutes.
Every step runs on your own machine, against a folder you are holding. Nothing here needs us to be online, or even to still exist.
- 01Download and build — free
The desktop app is a free download and the editor needs no licence at all. Start from an industry starting point, change a heading, and get to something you would genuinely put in front of a client.
- 02Export — the one step a licence unlocks
Everything up to the finish line is free — the editor, every starting point, every revision. The two paid actions are exporting the code and one-click deploy. On the cloud side that is Storefront Pro at $79/month; Storefront at $49/month publishes the site, and the source download is the Pro plan.
- 03Open the folder
Count the files. Read README.md, which is addressed to whoever inherits the site rather than to the person who built it. Then open package.json and look for a dependency with our name on it. There is not one.
- 04Run it
Run npm install, then npm run setup if the site has a database, then npm run dev. The storefront comes up on localhost:3000 and the back office on /admin, and the admin password is already waiting in the export’s .env — a fresh strong one minted per export, deliberately never echoed to a terminal or a build log. No key of any kind is needed to get that far.
- 05Cut us out
Search the folder for our name: comments and the footer credit, nothing else. Then take the machine off the network and load the site again. Everything still works. That is the entire guarantee, demonstrated in the only way that actually counts.
Or skip running the export yourself: a complete, untouched export is public on GitHub — the first commit is the export byte for byte, and the provenance note explains how to check that claim against the history. Read one on GitHub
04 · Which line to buy
Which line you want depends on who ends up holding the folder.
Both lines are built with the same editor. What differs is what exists at the end of the job.
LocalSite Studio — the handover line
$59/month, $490/year, or $699 once for the founding lifetime licence. Unlimited sites, unlimited exports, two machines per licence. Build for nothing and pay at the finish line. This is the line that puts files on a disk.
Naratake cloud — the hosted line
Storefront is $49/month or $468/year and publishes the site. Storefront Pro is $79/month or $758/year and adds the write side — the site’s own database and back office, where orders, reservations, appointments, customers and enquiries are stored — and it is the plan that includes downloading the source.