Who Owns an AI-Generated Website? Ownership Explained

You do. In Zugo the project belongs to the person who built it, and the practical proof is that the source exports to a GitHub repository under your own account, where it works without a Zugo account. What ownership does not settle is the material you put inside the page, a separate question with its own answer.

Ownership is easy to claim and awkward to verify, so the useful version of this post is not a reassurance. It is a list of what you are actually holding, where each piece lives, and how to check that the claim is real before you depend on it.

What does owning a website actually consist of?

Five distinct things, and people usually mean only one of them when they ask.

There is the code that makes the page work. There is the content inside it: your words, your photographs, your logo. There is the address people type. There is the data the site accumulates once real people use it. And there is the right to run a business on top of the whole arrangement.

Those five can be held by five different parties, which is exactly what goes wrong with tools where you assemble a site on a canvas and the site is not files. You own the content and the domain, and the thing that renders them belongs to somebody else.

Does the builder keep a claim on what it generated?

No. The project is yours, and the test of that statement is not a paragraph in a document, it is the export button. Sending the project to GitHub puts the files in a repository under your account, where you can clone them, read them, change them and run them.

That is the difference between ownership and permission. Permission is a tool letting you use something it controls, revocable in principle whenever its pricing or roadmap changes. Ownership is a copy in your hands that keeps working if the tool disappears tomorrow.

The way to make the claim concrete is to exercise it early. Build something small, export it, and open the repository. Ten minutes of that tells you more than any terms page, and it costs a fraction of a plan to find out.

Where does each piece of the project live?

In places you already control, once you have run the export.

The last row is the only one where something does not travel, and it is worth being precise about what it is. Your build history is the story of how the project was made. Losing it is losing notes, not losing the product.

The address row is the one that costs money to get wrong. A site that people have bookmarked at <slug>.zugo.run is portable but not free to move. Connecting a domain you own from the start makes the whole question moot, which is why it is worth doing on day one rather than after a launch.

What about the images, fonts and text inside the page?

They follow their own rules, and this is where an ownership claim quietly stops being about the builder.

Anything you wrote or photographed is yours and always was. Anything you uploaded from somewhere else carries whatever licence it came with, and putting it into a generated page does not launder that. A stock photo licensed for personal use is still licensed for personal use after a build.

The same applies to typefaces, icons and any snippet you pasted in from elsewhere. Before a project becomes commercial, walk through the page and ask where each visual asset came from. That review takes twenty minutes and it is far cheaper than the alternative. The practicalities of bringing your own material are in can I use my own images.

One honest caveat that no builder can resolve for you: how copyright applies to machine-generated material is treated differently in different jurisdictions and is still being worked out. If that distinction matters to your business, it is a question for a lawyer in your country rather than for any tool's documentation.

What does ownership not settle?

Four things, and they are the ones people discover late.

Permission to take money. Stripe approves your account for payments on its own terms. Owning the checkout page is not the same as being allowed to charge through it.

Tax and registration. Where the business is registered, what you owe and to whom is entirely outside the product, in every country.

Names and trademarks. A generator will happily build you a page for a brand name somebody else registered. Checking that is on you, before the logo goes anywhere.

Obligations to your users. A privacy policy, a way to delete an account, and whatever your jurisdiction requires about personal data. The data sits in your Supabase project, so you are able to honour those requests, and you are also the only one who will.

The broader version of this question, including what changes when you start charging, is in can I sell what I build.

What does it cost to reach a project you own?

Per action, published in advance.

The Free plan carries 5 credits once, less than one fresh build, so a real project starts on a paid plan. Pro is $25 per month with 200 credits, roughly 16 full platforms or 33 quick builds. Business is $99 per month.

The important structural point is that credits pay for generation, not for extraction. If getting your own code out required an escalating fee, the ownership claim would be decorative. The expensive part of any AI builder is making the thing, and that is where the price sits.

How do you make ownership real rather than theoretical?

Four moves, in this order, and none of them take long.

Connect a domain you own before you promote anything, so the address is yours from the first visitor. Keep the connectors in your own accounts, which is how Supabase and Stripe already work. Export to GitHub as soon as the project matters, and again before any risky round of changes, because a repository is cheap insurance. And keep your original images and copy somewhere outside the builder.

Done in that order, leaving any tool becomes a decision rather than an emergency, which is the only definition of ownership that survives contact with reality. Zugo does not replace a development team on a complex product, and the code being yours is precisely what makes bringing one in an upgrade instead of a rescue.

The mechanics of the export step are in can I export the code, and connecting an address you control is covered in can I use my own domain. To see what ownership contains rather than read about it, build something small at Zugo, push it to GitHub, and open the repository.