Every site gets an aveiro.page URL immediately, and you can point your own domain at it whenever you are ready. No build step to configure, no deploy pipeline to keep alive.
Locales that are content, not translation strings
Publish a different version of a page per locale, with a language switcher on the site. Each locale is real content you control rather than a machine pass over the original.
Output built for AI retrieval
Published sites expose llms.txt and a Markdown version of each page. When an assistant reads your documentation, it gets structured text instead of scraping rendered HTML.
Metadata and schema without the checklist
Titles, descriptions, canonicals, OpenGraph and structured data are generated from the page rather than filled in by hand on every route.
How a page goes live
01
Write it
In the editor, in MDX, or through the API from your own code.
02
Set the locales
Add the versions you want to serve and where the switcher should appear.
03
Publish the site
The page goes live with its metadata, sitemap entry and Markdown output.
Yes. Custom domains are available on paid plans; every site also keeps its aveiro.page address.
What exactly is llms.txt?
A machine-readable index of your published pages, served alongside a Markdown version of each one. It gives AI assistants a clean source to read instead of parsing your rendered HTML.
Do I need to manage a sitemap?
No. Published sites generate their own sitemap and robots file.
Is localization available on every plan?
Localization is a feature-gated capability — check the pricing page for the plan it is included on.