Do I own the code it writes?

Yes. It is a standard Next.js and React project, not a proprietary page format. Connect a GitHub repository and every build lands there as ordinary commits you can clone, edit in your own editor, and deploy anywhere else. Nothing about the output requires Zeplik to keep running it.

Where does my published site actually live?

On zeplik.app, which is a separate domain from the Zeplik product itself. That separation is deliberate and it protects you: your site's code and ours never share a domain, so nothing your site does can reach a Zeplik session and nothing a Zeplik session does can reach your visitors. Attaching your own domain replaces the address entirely.

Can I use my own domain name?

Yes. Point your domain at the project, and the certificate is issued and renewed automatically. Search engines are told your domain is the real address of the site, so the ranking you build belongs to your domain and not to a subdomain you are borrowing.

Can it build something with accounts and a database, not just pages?

Yes. Connect your own Supabase project and Zeplik wires sign-in, tables, and queries into the app as it builds. The database is yours, in your own account, so you keep direct access to your data and can revoke ours at any time.

What happens when the AI writes code that does not work?

It finds out before you do. Each build installs the project, runs a type check, compiles it, and loads every page in a real browser, and a failure is fed back with the actual error so the next attempt is aimed at the real cause. If it runs out of attempts it says what was still broken instead of handing you a site that looks finished and is not.

How is this different from asking a chatbot for code?

A chatbot gives you files and wishes you luck. Here the code is installed, compiled, opened in a browser, fixed when it fails, and put on a live URL, so what you are judging is a running site rather than a plausible-looking snippet. The whole loop happens in a sandbox with no access to your machine.

Building draws from your Zeplik credit balance like any other work on the platform, and you can start free. Hosting a published site is included. There is no separate seat, no per-site subscription, and nothing to cancel if you stop building.

AI website builder

Describe the site you want in plain sentences and Zeplik builds it: real pages, real code, running in a live preview you can watch. It installs the project, type-checks it, opens every page in a browser, and fixes what breaks before it hands anything to you. When you like it, publish it on a live address, or attach your own domain and make it yours.

Start building See finished sites See pricing

Free to start. Building uses your Zeplik credits; hosting a published site is included.

What you actually get

Every capability below with the part that is usually left out. A builder is only worth anything if you know where it stops.

Real code, not a locked template

You get a Next.js and React project with the files you would have written by hand. It is yours: connect GitHub and every change lands as a commit you can read, review, and take somewhere else.

It checks its own work

Every build installs, type-checks, compiles, and loads each page in a real browser before it is offered to you. When something breaks it reads the error and fixes it, and it tells you plainly when it could not.

A live preview while it works

The site runs in a sandbox from the first minute, so you watch it take shape instead of waiting for a finished artifact. The preview is private to your account, not a public URL anyone can find.

Editing by asking

Move the pricing section, change the tone of the copy, add a contact form. Targeted edits touch only the files they need, so an unrelated page cannot quietly change under you.

A database and sign-in when the site needs one

Connect your own Supabase project and the build wires auth, tables, and queries into the app. Your data stays in your account, under your credentials, not pooled in ours.

Published on an address you own

Every project gets a live subdomain the moment you publish, and you can attach your own domain with an automatic certificate. Unpublishing takes it offline immediately.

How it works

Describe the site
Write what it is for and who it is for, in ordinary sentences. A landing page for a coffee roaster with a menu and a booking form is enough to start; you do not need a spec, a wireframe, or a stack preference.
Watch it build, then steer
Zeplik plans the pages, writes the code, and runs it in a live preview. Follow along and redirect it while it works: different hero, cut the testimonials, make the whole thing darker.
Publish it
One action puts the site on a live address with HTTPS. Attach your own domain whenever you are ready, and republish any time you change something. Taking it down is one action too.

What people build with it

Landing pages that had to exist yesterday. A launch page, a waitlist, a one-pager for a service, live on a real domain the same day.
Small business sites. Menu, hours, gallery, contact form, and a booking link, without a template subscription or a plugin stack to maintain.
Internal tools. A dashboard over a table you already have, with sign-in, connected to your own database.
Portfolios and documentation. Structured content sites where the writing matters more than the framework, published and updated by asking.

Start from the kind of site you need

Each of these is a brief that has already been built and published by this product, with the finished site to look at and the exact prompt that produced it.

restaurant website builderA neighbourhood bistro with a menu and reservation details.photography portfolio website builderA landscape photographer's portfolio, captions and all.saas landing page builderA SaaS marketing site with pricing tiers and an FAQ.gym website builderA climbing gym with membership tiers and a class schedule.agency website builderA two-person design studio: manifesto, work, services.bakery website builderA sourdough bakery: today's bakes, the story, stockists.event website builderA one-day conference: speakers, schedule, venue and tickets.small shop website builderA houseplant shop: featured plants, care guides, visit us.author website builderA novelist's site: the latest book, the backlist, the author.travel blog and guide site builderA travel guide: itineraries, one in full, planning tips.nonprofit website builderA river cleanup nonprofit: mission, impact, volunteer, donate.podcast website builderA podcast: the latest episode, the archive, the hosts.

Where your site lives

Published sites are served from zeplik.app, a different domain from the Zeplik product on zeplik.ai. That is not an implementation detail, it is a safety property: your site and our application never share a domain, so a session on Zeplik is unreachable from code running on a published site, and one site cannot set anything that affects another. Every site is served host-only and isolated from its neighbours. When you attach your own domain it becomes the canonical address, and search engines are told so, which is why the ranking you earn stays with you if you ever leave.

Frequently asked questions

Do I own the code it writes?: Yes. It is a standard Next.js and React project, not a proprietary page format. Connect a GitHub repository and every build lands there as ordinary commits you can clone, edit in your own editor, and deploy anywhere else. Nothing about the output requires Zeplik to keep running it.
Where does my published site actually live?: On zeplik.app, which is a separate domain from the Zeplik product itself. That separation is deliberate and it protects you: your site's code and ours never share a domain, so nothing your site does can reach a Zeplik session and nothing a Zeplik session does can reach your visitors. Attaching your own domain replaces the address entirely.
Can I use my own domain name?: Yes. Point your domain at the project, and the certificate is issued and renewed automatically. Search engines are told your domain is the real address of the site, so the ranking you build belongs to your domain and not to a subdomain you are borrowing.
Can it build something with accounts and a database, not just pages?: Yes. Connect your own Supabase project and Zeplik wires sign-in, tables, and queries into the app as it builds. The database is yours, in your own account, so you keep direct access to your data and can revoke ours at any time.
What happens when the AI writes code that does not work?: It finds out before you do. Each build installs the project, runs a type check, compiles it, and loads every page in a real browser, and a failure is fed back with the actual error so the next attempt is aimed at the real cause. If it runs out of attempts it says what was still broken instead of handing you a site that looks finished and is not.
How is this different from asking a chatbot for code?: A chatbot gives you files and wishes you luck. Here the code is installed, compiled, opened in a browser, fixed when it fails, and put on a live URL, so what you are judging is a running site rather than a plausible-looking snippet. The whole loop happens in a sandbox with no access to your machine.
What does it cost?: Building draws from your Zeplik credit balance like any other work on the platform, and you can start free. Hosting a published site is included. There is no separate seat, no per-site subscription, and nothing to cancel if you stop building.

More on Zeplik

From a sentence to a live site

Describe it, watch it build, publish it on your own domain. The code is yours either way.

Start building Browse all tools