Same.new

What Same.new is

Same.new generates complete web pages from natural language and can clone the structure and style of an existing site from its URL, and the positioning is website generation with a cloning option. The aim is a page you describe, or one modelled on a site you point at.

What it does

The product generates full web pages from language and can clone the structure and style of an existing site by URL, with the directory noting cloning is supported and that copying a design may raise rights questions. The use cases are generating a page and copying a site's structure, which target two paths: describe what you want, or borrow the shape of something that already exists. Because cloning is offered, the value is speed from a reference, but the directory's own note about rights is the honest caveat, and the style of one site is not free to take. There is no claim that a clone is yours to ship, only that the structure can be reproduced.

Who it is for

People who want a page from a description, and those who like starting from a reference site's layout. It also suits quick builds where a model to react to beats a blank page.

What to keep in mind

Cloning raises the question the directory names, so handle it deliberately. Two points to weigh. First, copying the structure and style of an existing site can infringe someone's design or content rights, so do not ship a clone of a site you do not have permission to imitate, because a generated page modelled on another is still that other's work in substance. Second, confirm what you can do with anything generated, because a builder that gives you a page but will not let you export or host it freely is a demo, not a base. Keep Same.new for the page it generates, but clone only what you may, and own the output, because a website generator that supports cloning is most useful when the reference you use is one you are allowed to learn from.

Two cautions matter. New projects are public by default, so switch sensitive work to private immediately or design details can leak before you notice. And in-app deployment centres on a specific host, with no built-in custom-domain management, so larger projects need their own hosting plan. The reference-driven approach, rebuilding a URL or screenshot into an editable project, is the reason to use it, provided you have the rights to the material you are cloning.

Try it on a page you are authorised to rebuild, and switch the project to private before you paste anything sensitive. Check how faithfully it reproduces structure and how much you must correct, then confirm the deployment and custom-domain story if the page needs to live on your own address. The reference-driven approach is powerful, so the discipline of having the rights to the input matters as much as the output quality.