Skip to content

NewSites

Public docs, straight from your wiki. No copying, no second tool.

Turn projects and pages into public documentation, a help center or a changelog, on your own domain if you like and with an AI that answers only from your docs. Keep writing in the editor you know, check every release in a preview and publish with one click. Restricted pages never go public.

  • Included in every plan
  • Preview and rollback
  • Custom domain from Business
  • No cookies, no tracking

Why Sites

The docs live in the wiki. The public version lives somewhere else.

  1. Write twice, forget once

    Someone copies every internal update into the docs tool. Three releases later, one of them is wrong.

  2. Public often means instantly

    With many public wiki pages, every edit goes out right away, including the half sentence from a minute ago.

  3. One more tool to review

    Another tool means its own permissions, its own contract and its own data protection review.

With Sites, you publish your wiki pages as a fixed, reviewed release: from the same tool, with the same permission model.

What Sites do

Everything public docs need. From the wiki you already have.

One source, inside and out

Your public docs are your wiki pages. No export, no second editor, nothing to keep in sync. Real-time editing, comments and history work for everything that goes public, too.

Publish like a release

Every publish is a fixed release: check it in a preview, then take it live with one click. Rolling back to one of the last 20 releases is just as quick. If a build fails, the current release stays online.

Internal stays internal

Restricted, archived and deleted pages are left out with everything below them, even if the person publishing can see them. Links to internal pages turn into plain text; comments and boards stay out.

Navigation and search built in

Sidebar from your page tree, sections as tabs, table of contents, previous and next. Full-text search with Ctrl+K or ⌘K across the whole site, jumping straight to the right passage.

Your brand, your domain

Logo for light and dark, favicon, accent color, font and corner style, plus an announcement bar, links and fields for your legal notice and privacy policy. From Business with your own domain and custom CSS.

SEO-ready out of the box, ready for AI

Sitemap, canonical URLs, structured data and Open Graph previews on every page. For AI agents there is llms.txt, every page as Markdown and an MCP server for each site.

Templates

Three templates for docs, help and release notes.

Documentation

Sidebar, sections as tabs, table of contents, breadcrumbs and “last updated”. For product and developer docs.

Help center

A start page with a big search and topic cards, articles with full navigation. For your customers.

Changelog

Release notes as dated entries, newest first, with an Atom feed. Written right where you plan the release anyway.

Several sites per organization: 1 on Team, 10 on Business, as many as you need on Enterprise.

How it works

Live in three steps.

  1. Pick the content

    Create a site, choose a template and its sections: projects or pages with everything below them. Each section becomes a tab, in the order of your page tree.

  2. Check the preview

    UpSpec builds a fixed release in the background, with navigation, search and a Markdown version. A preview link shows it exactly as visitors will see it.

  3. Publish

    One click and the release is live. Keep writing in the wiki; UpSpec shows how many pages changed since, and you publish when the next release is ready.

Ask the docs

Questions in their own words. Answers from your docs.

In the search of every site, visitors can ask your organization’s AI. It answers only from the published release of that site, with numbered sources linking to the pages. If the docs don’t cover something, it says so.

Business and Enterprise

  • Only from the live release, and only from pages that are still public
  • Every answer is checked before anyone sees it: no valid source, no answer; no links, images or HTML from the model
  • Proof of work instead of a CAPTCHA, no third party, plus limits per visitor and per site and day
  • Its own monthly allowance, separate from your team’s AI budget
  • Questions are kept for 60 days, without IP addresses and with personal data masked, also towards the model
  • “Unanswered questions” show you where the docs have gaps

Uses the AI your organization has set up. Switched on per site, never in previews, no cookies.

Custom domains

Your docs on your own address.

Connect a domain such as docs.example.com to your site. Two DNS records are all it takes, and the TLS certificate is issued automatically.

Business and Enterprise

  • Proof of ownership via a TXT record, plus a CNAME or A/AAAA record pointing to UpSpec
  • TLS certificate issued automatically on the first visit
  • One primary address: all others redirect there with a 301, path included
  • Re-checked daily: if the records disappear, the domain is disconnected, to protect against domain takeover
  • Up to two custom domains per site

Search engines and AI agents

SEO-ready out of the box. Ready for AI agents.

Every site comes with what search engines and AI tools expect: ready-made HTML, clean URLs and machine-readable versions. Coding agents such as Claude Code or Cursor can also read your docs through an MCP server for each site.

  • Sitemap, robots.txt and canonical URLs, on your own domain too
  • Structured data (JSON-LD): website, articles and breadcrumbs
  • Open Graph previews when links are shared
  • llms.txt following llmstxt.org, llms-full.txt and every page as Markdown
  • MCP at /_mcp, read-only and without an account: search_docs, list_pages, read_page
  • Atom feed for the changelog
  • Stable URLs: renaming keeps the address, moved paths redirect with a 301

Statistics and feedback

See what gets read. Without cookies.

Every site counts page views and asks at the end of its pages: “Was this page helpful?” You see what gets read and where the docs fall short, without cookies and without data about readers.

  • Views through a tiny beacon; only daily totals per page are stored
  • Browsers with Do Not Track or Global Privacy Control are not counted, and neither are bots
  • Yes or no at the end of the pages, one vote per visitor, page and day
  • “Statistics” tab: 30 days with the trend, the most read pages and the least helpful ones
  • On every plan; feedback can be switched off per site

Privacy and security

Public does not mean wide open.

  • Restricted means gone, right away

    When a page is restricted, archived or deleted in the wiki, it disappears from the site at once. No republishing needed, and older releases are covered after a rollback, too.

  • Separate from the app

    Sites run on their own address, without sign-in, app session, cookies or tracking. App routes do not exist there.

  • Strict Content Security Policy

    Only the site’s own scripts run, and other sites cannot frame yours. Custom CSS cannot load anything from other servers either.

  • Hosted in Germany

    Sites run on the same platform as your wiki. Or on your own servers.

Pricing

Included in your plan.

Search, design, preview, rollback, sitemap, llms.txt, MCP, statistics and feedback come with every plan. Readers of your site need no account and do not count as a person.

  • Team

    1site

    • Custom domains (not included)
    • Site AI (not included)
    • Custom CSS (not included)
  • Business

    10sites

    • Custom domains (included)
    • Site AI (included)
    • Custom CSS (included)
  • Enterprise

    sites, no limit

    • Custom domains (included)
    • Site AI (included)
    • Custom CSS (included)
Compare plans

Questions

Questions about Sites

What is the difference between a public link and a site?

A public link shows a page or a subtree without sign-in, not indexed and always in its current state – good for sharing something quickly. A site is a website of its own with navigation, search, your design and a sitemap, on your own domain and open to search engines if you want. It always shows a published release, never changes nobody has approved yet.

Could something internal go public by accident?

Restricted, archived and deleted pages are never published, together with everything below them, even if the person publishing can see them. If a page is restricted, archived or deleted later, it disappears from the site at once, from older releases too. Links to pages outside the site turn into plain text, comments and boards stay internal, and the site only serves files that a published page shows. With “Leave out drafts”, pages with the status “Draft” stay internal as well. The site AI and the MCP server only see what the site shows publicly. You check every release first through a preview link that is valid for one hour and not indexed.

When do changes from the wiki appear on the site?

Only when you publish. That way every change goes out on purpose, and UpSpec shows how many pages changed since the live release. If you don’t like a new release, you put one of the last 20 back online with one click. Design settings such as color, logo or custom CSS, on the other hand, apply right away. And pages you restrict, archive or delete in the wiki disappear without a new publish.

How reliable is the site AI, and what does it cost?

The site AI answers only from the live release of your site and only from pages that may still be public; restricted content and other sites never reach the model. Personal data in questions, such as email addresses, phone numbers or keys, is masked before the question is stored or sent to the model. Every answer is checked before the visitor sees it: without a valid source, the visitor sees “This documentation does not cover that” instead of an answer, and links, images or HTML from the model never get through. Below every answer are the sources to read up on and a note that an AI wrote it. The site AI is included in Business and Enterprise and uses the AI your organization has set up. Against abuse there is a proof of work instead of a CAPTCHA, limits per visitor and per site and day, and its own monthly allowance, separate from your team’s AI budget. So visitors can never use up your team’s budget.

Can we use our own domain, such as docs.example.com?

Yes, on Business and Enterprise. Without a custom domain, every site runs on a default address from UpSpec, a subdomain of its own, separate from the app. For a custom domain, you add it to the site and create two DNS records: a TXT record that proves the domain is yours, and a CNAME pointing to UpSpec (for an apex domain without a subdomain, A and AAAA records). UpSpec checks this automatically, and the TLS certificate is issued on the first visit. Each site can have up to two custom domains; one is the primary address, and all other addresses redirect there with a 301. UpSpec re-checks the records daily: if they are missing several times in a row, the domain is disconnected to protect against domain takeover, and owners and admins get an email.

Do search engines and AI tools find sites?

Yes. Every site serves ready-made HTML with a sitemap, robots.txt, canonical URLs, structured data (JSON-LD) and Open Graph previews. For AI tools there is llms.txt following llmstxt.org, llms-full.txt with all pages, and every page as Markdown as well; a changelog has an Atom feed. Coding agents such as Claude Code or Cursor connect to the site’s MCP server at /_mcp without an account: read-only, with the tools search_docs, list_pages and read_page, rate-limited per visitor and switchable per site. Renamed pages keep their address, moved ones redirect with a 301. If a site should not appear in search engines, you switch indexing off.

How do statistics and feedback work without cookies?

Every page view sends a tiny beacon without a cookie. Only daily totals per page are stored, nothing about individual readers; UpSpec spots repeat views through a hash that expires after a short time. Browsers with Do Not Track or Global Privacy Control are not counted, and neither are bots. At the end of documentation and help center pages, readers see “Was this page helpful?”, with one vote per visitor, page and day. The “Statistics” tab shows the last 30 days with the trend, the most read pages and the ones that helped least. Both come with every plan; feedback can be switched off per site.

What is included in which plan?

Team includes 1 site, Business 10 and Enterprise as many as you need; the 30-day trial includes 10, like Business. Custom domains, the site AI and custom CSS come with Business and Enterprise. Search, custom design, preview, rollback, sitemap, llms.txt, Markdown for every page, the MCP server, statistics and feedback come with every plan. Readers of your site need no account and do not count as a person. If you move to a smaller plan, existing sites stay online, and you can create new ones once you are below the limit again. Without the Business features, custom domains are disconnected and the site AI and custom CSS are switched off; the site stays reachable at its default address.

Does a site use cookies or tracking?

No. A site sets no cookies and includes no tracking, not for statistics, feedback or the site AI either. Fonts and scripts are served by the site itself, embedded content such as videos loads only after a click, and custom CSS cannot load anything from other servers. Images you embed in pages from other servers are loaded from there by the browser. What only the visitor’s browser remembers: the chosen color scheme, a vote they cast, and access to the site AI for half an hour. You add links to your legal notice and privacy policy in the site’s design settings.

Can a site have several languages?

Each site has one language, German or English, which sets its interface and search. For a second language, create a second site. Several languages or versions within one site are not available yet.

Are Sites available when self-hosting?

Yes. You need a second domain with wildcard DNS and a wildcard certificate, separate from the app domain; without it, Sites are switched off. For custom domains, your edge proxy has to issue certificates on demand (on-demand TLS) and first ask UpSpec whether the domain is verified. Both are documented, with a tested example configuration for Caddy. The site AI uses the AI you have set up, including a model inside your own network.

Your docs are already written. Now they can go out.

Try everything in Business for 30 days, with up to 10 sites, your own domain and the site AI, no credit card.

No credit card · Cancel any month · Data in Germany