[site]
title: Micropage
description: Websites from a plain-text .page file, with accessibility and SEO built in. Add forms, a blog and a newsletter, and export the site whenever you want.
lang: en
keywords: static site from a text file, plain-text website builder, .page markup, static landing page with forms, Carrd alternative for developers, llms.txt markup for agents
logo: <- logo.svg
og_image: <- page.png
og_type: website

[blog]
title: Blog: Guides and Comparisons
description: Guides, how-tos and comparisons for building websites from a plain-text .page file: forms, custom domains, SEO, AI, and Carrd or Framer alternatives.

[site.dark]
logo: <- logo-dark.svg

[nav]
Home -> /
Tour -> /tour
Pricing -> /pricing
Showcase -> /showcase
Blog -> /content
FAQ -> /faq
Docs -> https://docs.micropage.sh
btn-outline: Login -> https://app.micropage.sh
btn: Start free -> https://app.micropage.sh

[footer]
/// section

col:
  p: Built with Micropage — no lock-in, just files

col:
  h5: Product
  link: Tour -> /tour
  link: Showcase -> /showcase
  link: Pricing -> /pricing
  link: Product facts -> /product

col:
  h5: Resources
  link: Docs -> https://docs.micropage.sh
  link: Blog -> /content
  link: FAQ -> /faq
  link: Markup for agents -> https://docs.micropage.sh/llms.txt

col:
  h5: Company
  link: Contact -> /contact
  link: Privacy -> /privacy
  link: Terms -> /terms

col:
  h5: Account
  link: Login -> https://app.micropage.sh
  link: Sign up -> https://app.micropage.sh

/// html
<script defer data-domain="micropage.sh" src="https://analytics.blckshp.xyz/js/plausible.js"></script>
<script>
window.plausible = window.plausible || function () { (window.plausible.q = window.plausible.q || []).push(arguments); };
(function () {
  function region(el) {
    if (el.closest('.mp-site-header')) return 'header';
    if (el.closest('.mp-site-footer')) return 'footer';
    if (el.closest('.mp-hero')) return 'hero';
    return 'body';
  }
  document.addEventListener('click', function (e) {
    var a = e.target.closest && e.target.closest('a[href^="https://app.micropage.sh"]');
    if (!a) return;
    plausible('App Click', { props: { location: region(a), label: (a.textContent || a.title || '').trim() } });
  });
  // The form script shows the success view only after a 201, so watching it counts real submissions.
  function watchForms() {
    document.querySelectorAll('[data-mp-form-success]').forEach(function (el) {
      var wrap = el.closest('[data-mp-form-wrap]');
      var nameInput = wrap && wrap.querySelector('input[name="form_name"]');
      var name = nameInput ? nameInput.value : 'unknown';
      var shown = false;
      new MutationObserver(function () {
        var visible = !el.classList.contains('d-none');
        if (visible && !shown) plausible('Form Submit', { props: { form: name } });
        shown = visible;
      }).observe(el, { attributes: true, attributeFilter: ['class'] });
    });
  }
  if (document.readyState === 'loading') document.addEventListener('DOMContentLoaded', watchForms);
  else watchForms();
})();
</script>
<div></div>

[Home -> /]
meta:
  title: Your website is a text file
  description: A website from a plain-text .page file: static HTML with forms, posts and a newsletter, accessibility and SEO built in from the start. Export the site any time.
  og_type: website

/// hero
h1: Your website is a text file.
h2: Accessibility and SEO built in from the start.
p: Write a .page file and publish it as static HTML with working forms. The file is yours, and so is the site it makes: export it as plain HTML in one download and host it anywhere.
button: Start free -> https://app.micropage.sh
btn-secondary: See real .page files -> /showcase
small: Pro, $6 a month: your own domain, the CLI and MCP server, a zip of the built site, newsletter sending and five projects.

col:
  img: Two panels side by side. On the left, a short .page file for Wit in a dark code editor, twelve lines long: a site block with the title Wit, the language en and the primary colour #b5441b; a Home page; and a hero with the heading Wit, a free writing app, an image described as A manuscript open in Wit, and a Download button. An arrow points right to the second panel, the published usewit.app homepage in a browser window: the wit. logo, a menu with Features, Open Source, GitHub and an orange Download button, the heading Write simply. Publish beautifully., a one-sentence description, Download Wit and Explore features buttons, and below them a screenshot of the Wit editor with a manuscript on the left and its typeset pages on the right. <- hero-file-to-site.png
  link: Read the full usewit.app file <- showcase-usewit-app.txt
  link: This page is a file too <- showcase-micropage-sh.txt

/// html
<style>
.mp-code{
  display:block;
  text-align:left;
  max-width:100%;
  margin:0 0 1.25rem;
  padding:1rem 1.25rem;
  background:var(--bs-secondary-bg);
  border:1px solid var(--bs-border-color);
  border-radius:.5rem;
  overflow-x:auto;
  font-size:.8rem;
  line-height:1.55;
  color:var(--bs-body-color);
}
.mp-code code{
  font-family:var(--bs-font-monospace, ui-monospace, SFMono-Regular, Menlo, monospace);
  white-space:pre-wrap;
}
.mp-section-intro .mp-code{
  display:inline-block;
  min-width:18rem;
  margin:0 auto 1.25rem;
}
/* The tagline under the title: a heading for the outline, sized as a subtitle. */
.mp-hero .mp-hero-copy h2{
  font-size:clamp(1.125rem, 1rem + .6vw, 1.5rem);
  font-weight:500;
  letter-spacing:-.01em;
  color:var(--bs-secondary-color);
  margin:-.5rem 0 1rem;
}
/* The file-to-site picture runs the full width under the hero copy. */
.mp-hero .mp-hero-frame{
  padding:2rem 0 clamp(2rem, 4vw, 3.5rem);
}
.mp-hero .mp-section-row{
  padding-top:0 !important;
}
.mp-hero .mp-column{
  text-align:center !important;
}
.mp-hero .mp-column .mp-image{
  width:100%;
}
.mp-hero .mp-column .mp-image-block{
  margin-bottom:1.25rem;
}
/* The form and the submission pictures have different shapes; split the row so they come out the same height. */
@media (min-width: 992px){
  .mp-section:has(img[alt*="Submission details"]) .mp-section-row > .mp-column:first-child{
    flex:0 0 41%;
    max-width:41%;
  }
  .mp-section:has(img[alt*="Submission details"]) .mp-section-row > .mp-column:last-child{
    flex:0 0 59%;
    max-width:59%;
  }
}
</style>
<div></div>

/// section bg:muted
h2: Why this exists
p: I'm visually impaired, and most website builders assume you can drag blocks around a visual canvas. I can't do that reliably, but I can work in text and with a keyboard all day. So I built Micropage: one .page file per site, published as static HTML. I use it for every site I run.
p: Cosmin Stefaniga

/// section
h2: Accessibility and SEO, with nothing to configure
p: You focus on your content. The defaults are taken care of, on every page, from the first publish.

col:
  icon: bi bi-universal-access
  h3: Accessible by default
  - Text on a theme colour comes out black or white, whichever has more contrast by the WCAG formula. Buttons follow.
  - The words before an image's file become its alt text, so describing the picture is how you add one.
  - Every page has a skip link, labelled landmarks, visible keyboard focus and the heading levels you wrote.
  - Every form field has a label, and errors and the success message are announced.
  link: What every page includes -> https://docs.micropage.sh/docs/concepts/accessibility/

col:
  icon: bi bi-search
  h3: Found by search engines by default
  - sitemap.xml and robots.txt, generated on every publish.
  - Canonical URLs, titles, descriptions and Open Graph tags from your markup.
  - Structured data for the site and for every post.
  - A noindex line keeps any page out of the index.
  link: SEO and social cards -> /content/seo-for-your-micropage-site

/// section
h2: One way to write each thing
p: .page is not Markdown. It's a small, closed grammar for the things a site needs and Markdown doesn't have: nav, sections, columns, buttons and forms. One element per line, no nested tags, no arbitrary CSS. The whole reference is about 120 lines.

col:
  h3: Nothing to invent
html: <p>There is one spelling for each thing: <code>-&gt;</code> is always a link, <code>&lt;-</code> is always a file from your folder, <code>col:</code> is always a column. That keeps diffs clean and mistakes local. It's also why agents get it right: the vocabulary is closed, so the editor's AI tab and your own agent, through the MCP server, have nothing to invent.</p>
  link: Why the markup was designed this way -> /content/designing-markup-for-ai-agents

col:
  h3: One escape hatch
html: <p><code>/// html</code> is the escape hatch: raw HTML for embeds and the few things the grammar doesn't cover. Everything else stays in the vocabulary, so a file reads the same whoever wrote it.</p>
  link: The whole grammar, about 120 lines -> https://docs.micropage.sh/llms.txt

col:
  h3: What it's for
  p: Landing pages, multi-page sites and blogs, with forms and a newsletter. Posts are Markdown, published at /content with an RSS feed, so the page grammar can stay small. Not for app UIs, pixel-perfect design or design systems; use Framer, Webflow or a frontend stack for those.
  link: Why a custom markup language -> /content/why-a-custom-markup-language

/// section
h2: What's built in

col:
  icon: bi bi-ui-checks
  h3: Forms
  p: Submissions land in the editor, so a landing page needs no backend. Turnstile and a spam filter keep bots out. CSV export and an email digest on Pro; webhooks and instant email on Pro+.

col:
  icon: bi bi-envelope-paper
  h3: Newsletter
  p: Turn any form into a signup. Subscribers live in the editor. Sending broadcasts is on Pro.

col:
  icon: bi bi-journal-text
  h3: Posts
  p: Markdown files with front matter, published at /content with RSS, from the editor or the CLI. On Pro, posts can also go out to subscribers.

col:
  icon: bi bi-cloud-upload
  h3: Publishing
  p: Static HTML served from Cloudflare's network over HTTPS. On Pro+, a publish is live in about 10 seconds; on Free and Pro, builds wait about 3 minutes in a queue first. Every build is numbered and can be rolled back.

/// section
h2: A form is three lines
p: Three lines from lantern.travel's file, the form they publish, and a submission as it arrives in the editor.
html: <pre class="mp-code" tabindex="0" aria-label="The three lines in lantern.travel's .page file that make its waitlist form"><code>form: waitlist&#10;input: Email*&#10;submit: Join the waitlist</code></pre>
link: How forms work -> /content/how-forms-work-in-micropage

col:
  h3: The form it publishes
  img: alt: The waitlist form on lantern.travel, with a note that an asterisk marks a required field, an Email field, a Cloudflare Turnstile box reading Verify you are human, and a Join the waitlist button <- home-form-lantern.png

col:
  h3: A submission in the editor
  img: alt: The editor's Submission details panel, listing a submission ID, the form name waitlist, the page URL, the time submitted, and the payload as JSON with one Email field <- home-form-submission.png

/// section bg:muted
h2: Export the site and leave
p: The source file is yours on every plan. On Pro, download the whole site and host it wherever you want.

col:
  icon: bi bi-file-earmark-text
  h3: The file
  p: Plain text, on every plan. Read it or copy it from the editor, or keep it in your own repo with the CLI on Pro.

col:
  icon: bi bi-file-earmark-zip
  h3: The built site
  p: On Pro, download any build as a zip of plain HTML, CSS and fonts. It runs on any host: your own server, Netlify, Cloudflare Pages or GitHub Pages. Submissions and subscribers download as CSV.

/// section
h2: On Pro, $6 a month or $49 a year

col:
  icon: bi bi-globe2
  h3: Your own domain
  p: Point a subdomain like www at Micropage with one DNS record; HTTPS is set up and renewed for you. For the bare domain, add a redirect to www at your DNS provider.

col:
  icon: bi bi-terminal
  h3: The CLI
  p: Install with Homebrew or npm. The .page file lives in your repo and micropage publish deploys it. Pro+ adds deploy tokens, so GitHub Actions can publish.

col:
  icon: bi bi-robot
  h3: MCP server
  p: Connect Claude Code, Claude Desktop, Cursor or VS Code, and your agent creates, edits and publishes pages and posts the way the CLI does. Sending email and deleting projects are off by default.
  link: Set it up -> https://docs.micropage.sh/docs/mcp/overview/

/// section
h2: What a published page loads
p: Static HTML and one first-party stylesheet trimmed to that site.

col:
  h3: One stylesheet, 8 to 12 KB
  p: Bootstrap compiled and purged against that site's HTML, gzipped. Fonts are self-hosted. Dark mode follows the visitor's OS in CSS, with no theme script.

col:
  h3: Almost no JavaScript
  p: Small inline scripts for the mobile menu and nav dropdowns, only on sites that have them. No framework, no Bootstrap JS, no error reporting.

col:
  h3: Nothing third-party
  p: Unless you add it yourself in a /// html block. The one exception: Cloudflare Turnstile on pages with a form, to keep spam out.

/// section
h2: Sites running on it
p: Each one links to the file it was published from.
link: Every site, with its source -> /showcase

col:
  img: alt: usewit.app homepage <- showcase-usewit-app.png
  h3: usewit.app
  p: Wit, a free, open-source editor for books and scripts. One file.
  link: Website -> https://www.usewit.app
  link: Source <- showcase-usewit-app.txt

col:
  img: alt: maproll.io homepage <- showcase-maproll-io.png
  h3: maproll.io
  p: Choropleth maps from a URL. Eleven pages across eight .page files, plus a weekly blog.
  link: Website -> https://maproll.io
  link: Source <- showcase-maproll-io.txt

col:
  img: alt: micropage.sh homepage <- showcase-micropage-sh.png
  h3: micropage.sh
  p: This site: home, pricing, tour, FAQ and showcase from one file. The blog is Markdown posts.
  link: Website -> https://micropage.sh
  link: Source <- showcase-micropage-sh.txt

/// section
h2: Pricing
p: Carrd is cheaper. Framer is prettier. Micropage is the page you still own as a file.
link: Compare plans -> /pricing

col:
  icon: bi bi-gift
  h3: Free
  p: See if the format clicks.
  p: $0
  p: 1 project · web editor with monthly AI credits · 100 form submissions
  p: On a micropage.sh subdomain, with a badge. No CLI, custom domain or zip.

col:
  icon: bi bi-star-fill
  h3: Pro
  p: Launch a real site.
  p: $6/mo · $49/year
  p: Your domain, the CLI, MCP server, zip export, newsletter sending, CSV, no badge
  p: 5 projects · 1,000 submissions/month

col:
  icon: bi bi-lightning-charge-fill
  h3: Pro+
  p: Operate it.
  p: $12/mo · $98/year
  p: Webhooks, CI deploy tokens, instant email, 20 projects
  p: 10,000 submissions/month

/// section align:center
h2: Start with one file
p: Free for one site on a micropage.sh subdomain, no card. If the format doesn't click, you stop, and the .page file is still yours.
button: Start free -> https://app.micropage.sh
btn-outline: Read the docs -> https://docs.micropage.sh
link: Pricing -> /pricing

/// html
<script type="application/ld+json">
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://micropage.sh/#organization","name":"Micropage","url":"https://micropage.sh","email":"hey@micropage.sh","sameAs":["https://github.com/micropage-sh"],"founder":{"@type":"Person","@id":"https://micropage.sh/#founder","name":"Cosmin Stefaniga","sameAs":["https://x.com/cosminstefaniga","https://www.linkedin.com/in/cosminstefaniga/"]}},{"@type":"SoftwareApplication","@id":"https://micropage.sh/#software","name":"Micropage","applicationCategory":"DeveloperApplication","operatingSystem":"Web","url":"https://micropage.sh","description":"Websites from a plain-text .page file, with accessibility and SEO built in. Add forms, a blog and a newsletter, and export the site whenever you want.","offers":{"@type":"Offer","price":"0","priceCurrency":"USD","description":"Free: one project on a micropage.sh subdomain, web editor with monthly AI credits, 100 form submissions"},"publisher":{"@id":"https://micropage.sh/#organization"}}]}
</script>
<div></div>

[Pricing -> /pricing]
meta:
  title: Free to publish, Pro from $6/mo
  description: Micropage pricing — free to publish on a subdomain with AI credits that refill monthly. Pro adds your domain, zip export, the CLI and the MCP server.
  og_type: website

/// section
icon: bi bi-stopwatch
h2: Pay when the page has to look like yours
p: Free publishes a real site. Pro is the plan for a custom domain, a zip of the build, and no badge.

/// section
icon: bi bi-tags
h1: Pricing
p: Start free — no credit card. Upgrade when you need a domain, export, or more than one project.

/// section
h2: Compare plans

/// html
<style>
/* projects/micropage: pricing comparison (bundled with this page) */
.micropage-pricing-table {
  margin: 0.5rem 0 1.25rem;
  color: var(--bs-body-color);
}
.micropage-pricing-table .mp-pricing-table-container {
  width: 100%;
  padding-inline: clamp(0.75rem, 3vw, 1.5rem);
  box-sizing: border-box;
}
.micropage-pricing-table .mp-pricing-table-inner {
  width: 100%;
  max-width: 1120px;
  margin-inline: auto;
  box-sizing: border-box;
  overflow-x: auto;
}
.micropage-pricing-table table {
  width: 100%;
  border-collapse: collapse;
  font-size: 0.9rem;
  line-height: 1.35;
}
.micropage-pricing-table caption {
  text-align: left;
  font-weight: 600;
  margin-bottom: 0.5rem;
  color: var(--bs-heading-color);
}
.micropage-pricing-table th,
.micropage-pricing-table td {
  border: 1px solid var(--bs-border-color);
  padding: 0.5rem 0.6rem;
  vertical-align: top;
  color: var(--bs-body-color);
}
.micropage-pricing-table thead th {
  background: var(--bs-secondary-bg);
}
.micropage-pricing-table .mp-plan-pro {
  background: var(--bs-primary-bg-subtle);
}
.micropage-pricing-table .mp-plan-name {
  font-weight: 700;
  text-transform: uppercase;
  letter-spacing: 0.03em;
  font-size: 0.8rem;
  color: var(--bs-heading-color);
}
.micropage-pricing-table .mp-tagline {
  color: var(--bs-secondary-color);
  font-size: 0.8rem;
  font-weight: normal;
  text-transform: none;
  letter-spacing: normal;
  display: block;
  margin-top: 0.25rem;
}
.micropage-pricing-table .mp-price {
  font-weight: 700;
  display: block;
  color: var(--bs-heading-color);
}
.micropage-pricing-table .mp-price-block {
  margin-top: 0.35rem;
}
.micropage-pricing-table[data-billing="monthly"] .mp-price--yearly,
.micropage-pricing-table[data-billing="monthly"] .mp-yearly-hint {
  display: none !important;
}
.micropage-pricing-table[data-billing="yearly"] .mp-price--monthly {
  display: none !important;
}
.micropage-pricing-table .mp-yearly-hint {
  font-size: 0.75rem;
  font-weight: 500;
  color: var(--bs-secondary-color);
  margin-top: 0.2rem;
}
.micropage-pricing-table .mp-billing-toggle {
  display: flex;
  flex-wrap: wrap;
  justify-content: center;
  gap: 0;
  margin: 0 auto 1rem;
  max-width: 22rem;
  border: 1px solid var(--bs-border-color);
  border-radius: var(--mp-btn-radius, 0.375rem);
  overflow: hidden;
  background: var(--bs-secondary-bg);
}
.micropage-pricing-table .mp-billing-toggle__btn {
  flex: 1 1 50%;
  font: inherit;
  font-size: 0.875rem;
  padding: 0.55rem 0.75rem;
  border: none;
  background: transparent;
  cursor: pointer;
  color: var(--bs-body-color);
  line-height: 1.2;
}
.micropage-pricing-table .mp-billing-toggle__btn + .mp-billing-toggle__btn {
  border-left: 1px solid var(--bs-border-color);
}
.micropage-pricing-table .mp-billing-toggle__btn.is-active {
  background: var(--bs-tertiary-bg);
  font-weight: 600;
  color: var(--bs-heading-color);
}
.micropage-pricing-table .mp-billing-toggle__hint {
  display: block;
  font-size: 0.65rem;
  font-weight: 500;
  color: var(--bs-secondary-color);
  margin-top: 0.15rem;
}
.micropage-pricing-table .mp-badge {
  display: inline-block;
  font-size: 0.65rem;
  font-weight: 600;
  text-transform: uppercase;
  background: var(--bs-primary);
  color: var(--mp-primary-contrast, #fff);
  padding: 0.15rem 0.4rem;
  border-radius: 0.25rem;
  margin-bottom: 0.25rem;
}
.micropage-pricing-table tbody th {
  text-align: left;
  font-weight: 600;
  color: var(--bs-heading-color);
}
.micropage-pricing-table .mp-cell {
  text-align: center;
}
.micropage-pricing-table .mp-miss {
  color: var(--bs-secondary-color);
  font-size: 1.1rem;
  opacity: 0.85;
}
.micropage-pricing-table .mp-hit {
  color: var(--bs-success);
  font-weight: 600;
}
@media (prefers-color-scheme: dark) {
  .micropage-pricing-table .mp-hit {
    color: #75b798;
  }
}
.micropage-pricing-table .visually-hidden {
  position: absolute;
  width: 1px;
  height: 1px;
  padding: 0;
  margin: -1px;
  overflow: hidden;
  clip: rect(0, 0, 0, 0);
  white-space: nowrap;
  border: 0;
}
</style>
<div id="mp-pricing-widget" class="micropage-pricing-table" data-billing="monthly">
  <div class="mp-pricing-table-container">
    <div class="mp-pricing-table-inner">
  <div class="mp-billing-toggle" role="group" aria-label="Billing period">
    <button type="button" class="mp-billing-toggle__btn is-active" data-mp-billing="monthly" aria-pressed="true">
      Monthly
    </button>
    <button type="button" class="mp-billing-toggle__btn" data-mp-billing="yearly" aria-pressed="false">
      Yearly
      <span class="mp-billing-toggle__hint">Save 32%</span>
    </button>
  </div>
<table>
  <caption class="visually-hidden">Plan comparison: Free, Pro, and Pro+</caption>
  <thead>
    <tr>
      <th scope="col"></th>
      <th scope="col" class="mp-cell">
        <span class="mp-plan-name">Free</span>
        <span class="mp-tagline">See if the markup clicks</span>
        <span class="mp-price">$0</span>
      </th>
      <th scope="col" class="mp-cell mp-plan-pro">
        <span class="mp-badge">Most popular</span><br />
        <span class="mp-plan-name">Pro</span>
        <span class="mp-tagline">Launch a real site</span>
        <span class="mp-price-block">
          <span class="mp-price mp-price--monthly">$6/mo</span>
          <span class="mp-price mp-price--yearly">$49/year</span>
          <span class="mp-yearly-hint mp-price--yearly">Save 32%</span>
        </span>
      </th>
      <th scope="col" class="mp-cell">
        <span class="mp-plan-name">Pro+</span>
        <span class="mp-tagline">Operate it</span>
        <span class="mp-price-block">
          <span class="mp-price mp-price--monthly">$12/mo</span>
          <span class="mp-price mp-price--yearly">$98/year</span>
          <span class="mp-yearly-hint mp-price--yearly">Save 32%</span>
        </span>
      </th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <th scope="row">Projects</th>
      <td class="mp-cell">1</td>
      <td class="mp-cell mp-plan-pro">5</td>
      <td class="mp-cell">20</td>
    </tr>
    <tr>
      <th scope="row">Asset storage</th>
      <td class="mp-cell">25 MB / project</td>
      <td class="mp-cell mp-plan-pro">100 MB / project</td>
      <td class="mp-cell">500 MB / project</td>
    </tr>
    <tr>
      <th scope="row">Form submissions</th>
      <td class="mp-cell">100</td>
      <td class="mp-cell mp-plan-pro">1,000 / month</td>
      <td class="mp-cell">10,000 / month</td>
    </tr>
    <tr>
      <th scope="row">AI credits</th>
      <td class="mp-cell">Free credit every month</td>
      <td class="mp-cell mp-plan-pro">More each month</td>
      <td class="mp-cell">Most each month</td>
    </tr>
    <tr>
      <th scope="row">Email notifications</th>
      <td class="mp-cell"><span class="mp-miss" aria-label="Not included">✕</span></td>
      <td class="mp-cell mp-plan-pro">Daily digest</td>
      <td class="mp-cell">Instant + webhook</td>
    </tr>
    <tr>
      <th scope="row">Form submissions CSV export</th>
      <td class="mp-cell"><span class="mp-miss" aria-label="Not included">✕</span></td>
      <td class="mp-cell mp-plan-pro"><span class="mp-hit" aria-label="Included">✓</span></td>
      <td class="mp-cell"><span class="mp-hit" aria-label="Included">✓</span></td>
    </tr>
    <tr>
      <th scope="row">Download build archive (.zip)</th>
      <td class="mp-cell"><span class="mp-miss" aria-label="Not included">✕</span></td>
      <td class="mp-cell mp-plan-pro"><span class="mp-hit" aria-label="Included">✓</span></td>
      <td class="mp-cell"><span class="mp-hit" aria-label="Included">✓</span></td>
    </tr>
    <tr>
      <th scope="row">Custom domains</th>
      <td class="mp-cell"><span class="mp-miss" aria-label="Not included">✕</span></td>
      <td class="mp-cell mp-plan-pro"><span class="mp-hit" aria-label="Included">✓</span></td>
      <td class="mp-cell"><span class="mp-hit" aria-label="Included">✓</span></td>
    </tr>
    <tr>
      <th scope="row">CLI access</th>
      <td class="mp-cell"><span class="mp-miss" aria-label="Not included">✕</span></td>
      <td class="mp-cell mp-plan-pro"><span class="mp-hit" aria-label="Included">✓</span></td>
      <td class="mp-cell"><span class="mp-hit" aria-label="Included">✓</span></td>
    </tr>
    <tr>
      <th scope="row">MCP server for AI agents</th>
      <td class="mp-cell"><span class="mp-miss" aria-label="Not included">✕</span></td>
      <td class="mp-cell mp-plan-pro"><span class="mp-hit" aria-label="Included">✓</span></td>
      <td class="mp-cell"><span class="mp-hit" aria-label="Included">✓</span></td>
    </tr>
    <tr>
      <th scope="row">No branding</th>
      <td class="mp-cell"><span class="mp-miss" aria-label="Not included">✕</span></td>
      <td class="mp-cell mp-plan-pro"><span class="mp-hit" aria-label="Included">✓</span></td>
      <td class="mp-cell"><span class="mp-hit" aria-label="Included">✓</span></td>
    </tr>
    <tr>
      <th scope="row">CI / deploy tokens</th>
      <td class="mp-cell"><span class="mp-miss" aria-label="Not included">✕</span></td>
      <td class="mp-cell mp-plan-pro"><span class="mp-miss" aria-label="Not included">✕</span></td>
      <td class="mp-cell"><span class="mp-hit" aria-label="Included">✓</span></td>
    </tr>
    <tr>
      <th scope="row">Priority build queue</th>
      <td class="mp-cell"><span class="mp-miss" aria-label="Not included">✕</span></td>
      <td class="mp-cell mp-plan-pro"><span class="mp-miss" aria-label="Not included">✕</span></td>
      <td class="mp-cell"><span class="mp-hit" aria-label="Included">✓</span></td>
    </tr>
  </tbody>
</table>
    </div>
  </div>
<script>
(function () {
  var root = document.getElementById('mp-pricing-widget');
  if (!root) return;
  var buttons = root.querySelectorAll('.mp-billing-toggle__btn[data-mp-billing]');
  function setBilling(period) {
    root.setAttribute('data-billing', period);
    buttons.forEach(function (btn) {
      var on = btn.getAttribute('data-mp-billing') === period;
      btn.classList.toggle('is-active', on);
      btn.setAttribute('aria-pressed', on ? 'true' : 'false');
    });
  }
  root.querySelector('.mp-billing-toggle').addEventListener('click', function (e) {
    var t = e.target.closest('[data-mp-billing]');
    if (!t || !root.contains(t)) return;
    setBilling(t.getAttribute('data-mp-billing'));
  });
})();
</script>
</div>

/// section
p: Billing runs through Paddle in the web app. Prices are in US dollars and exclude VAT and sales tax, which Paddle adds for your country at checkout. Carrd wins on price. Micropage wins if you want a file in git and an agent that won't invent components.
button: Start free -> https://app.micropage.sh
btn-outline: View docs -> https://docs.micropage.sh

/// section
h2: You own the output
p: The source file is yours on every plan. The built site is yours on Pro.

col:
  h3: The .page file
  p: Plain text on every plan, including Free. Read it or copy it from the editor, or keep it in your own repo with the CLI on Pro.

col:
  h3: The built site
  p: Pro and Pro+ download any build as a zip of plain HTML, CSS and fonts. It opens from disk and runs on any host.

/// section
h2: What changes when you upgrade?

col:
  icon: bi bi-globe2
  p: Your own domain

col:
  icon: bi bi-download
  p: Zip the static build · export submissions

col:
  icon: bi bi-eye-slash
  p: Remove the Micropage badge

col:
  icon: bi bi-robot
  p: More AI credits each month, CLI, and on Pro+ CI tokens

/// section
h2: FAQ

col:
  h3: Can I switch plans anytime?
  p: Yes. Upgrade or downgrade from your account. Changes usually apply on the next billing cycle.

col:
  h3: Do I need to pay to publish?
  p: No. Free publishes on a micropage.sh subdomain and includes an AI credit that refills every month, so you can keep generating.

col:
  h3: When do I need Pro?
  p: Custom domain, zip export, CLI, MCP server, CSV, email digest, five projects, or no badge.

col:
  h3: What happens if I exceed limits?
  p: You'll be asked to upgrade before you can go past them.

col:
  h3: How does billing work?
  p: Paid plans are billed through Paddle in the web app. Prices exclude VAT and sales tax; Paddle adds the tax for your country at checkout. Invoices live in your account.

[Tour -> /tour]
meta:
  title: The editor: markup, AI, forms, live preview
  description: A tour of the Micropage editor — markup and preview, AI generation, forms, newsletter, and builds you can roll back or download.

/// section
icon: bi bi-binoculars
h1: A tour of the editor
p: How writing, forms, the newsletter and builds work in the editor.

/// section
h2: Markup on the left. Live preview on the right.

col:
  h3: Edit a .page file like code
  p: The source pane is plain text. Headings, paragraphs, columns, sections — one element per line, no nesting bugs. Save and the right pane re-renders.
  p: Switch to the AI tab and prompt instead. Both paths produce the same markup. You can keep editing it in the browser, in vim, or via an agent.

col:
  img: alt: Micropage editor source pane and live preview <- tour-editor.png

/// section
h2: Forms with CSV export. Webhooks on Pro+.

col:
  img: alt: Form submissions dashboard in Micropage <- tour-forms.png

col:
  h3: No backend to write
  p: Drop a form block into the markup, publish, and submissions start landing. Storage is included. CSV export and a daily email digest ship on Pro.
  p: Pro+ posts every submission to a webhook you choose. The payload includes project id, form name, page URL, and the full field map.
  link: How forms work -> /content/how-forms-work-in-micropage

/// section
h2: Newsletter — subscribers and broadcasts

col:
  h3: Capture leads, send updates
  p: Toggle Newsletter on any form and submissions become subscribers instead of one-off rows. Welcome emails fire on signup. From-name and reply-to live in sender settings.
  p: Broadcasts are markdown, with preview, send-to-myself, and a delivery report. No third-party email tool.

col:
  img: alt: Newsletter broadcasts composer <- tour-newsletter.png

/// section
h2: Builds, rollback, and a zip you can take with you

col:
  img: alt: Build history with rollback <- tour-builds.png

col:
  h3: Every deploy is reversible
  p: Each publish creates a numbered build. Rollback is one click. The current build's status is on every screen.
  p: Pro downloads any build as a static .zip — host it on Cloudflare Pages, Netlify, S3, or your own server. Pro+ adds deploy tokens so CI can publish the repo.

/// section align:center
icon: bi bi-rocket-takeoff
h2: Ready to try it?
p: Free publishes a real site and includes an AI credit that refills every month. Pro from $6/mo.
button: Start free -> https://app.micropage.sh
btn-outline: View docs -> https://docs.micropage.sh

[FAQ -> /faq]
meta:
  title: The .page file, AI, forms, domains, export
  description: Common questions about Micropage — the .page file, AI generation, forms, custom domains, and exporting your site.

/// section
icon: bi bi-question-circle
h1: Frequently asked

/// section

col:
  h3: What is Micropage, and is it the same as a "micro page"?
  p: A micro page is a general term for a single-purpose site. Micropage is a website builder: pages, blogs, forms and newsletters from a plain-text file. You write or generate a .page file, it compiles to static HTML with working forms, and you host it on a micropage.sh subdomain or your own domain.

col:
  h3: What is a .page file?
  p: A plain-text markup file — like Markdown, but built for websites. Headings, paragraphs, columns, and sections use line-prefix tags. Micropage compiles it to static HTML. Editable in any text editor.

col:
  h3: Do I need to know how to code?
  p: No. If you can use Markdown, you can use Micropage. Or prompt the AI tab and tweak the result.

col:
  h3: What's on the free plan?
  p: One project, a micropage.sh subdomain, 100 form submissions, the Micropage badge, and an AI credit that refills every month.

col:
  h3: Can my AI assistant edit my pages?
  p: Yes. The grammar is small and closed, so agents write valid markup. Point an agent at the project (PROJECT_AGENT.md ships with it), or on Pro connect it through the MCP server.

col:
  h3: Can I use my own domain?
  p: Yes, on Pro. CNAME the subdomain to cname.micropage.sh. We issue and renew the certificate.
  link: Step-by-step guide -> /content/connect-your-own-domain

col:
  h3: Can I export my site and host it elsewhere?
  p: The .page source is always yours. Pro downloads any build as a static .zip. Cloudflare Pages, Netlify, S3, your own server.

col:
  h3: How do form submissions work?
  p: Stored per project. CSV export and email digest on Pro. Webhook delivery on Pro+. No backend to write.

col:
  h3: Can I collect newsletter subscribers?
  p: Yes. Toggle Newsletter on a form. Broadcasts, welcome emails, and a delivery report live in the editor. Sending is on Pro.

col:
  h3: Is there a CLI?
  p: Yes, on Pro. brew tap micropage-sh/tap && brew install micropage, or npm install -g @micropage-sh/cli. Pull, edit locally, publish. Deploy tokens on Pro+ make it CI-friendly.

col:
  h3: What about SEO?
  p: Auto sitemap and robots.txt. Per-page titles, descriptions, and OG tags from the markup. It's static HTML.
  link: SEO and social cards -> /content/seo-for-your-micropage-site

col:
  h3: What does Micropage do for accessibility?
  p: Text on your theme colours is picked by WCAG contrast, the words before an image's file become its alt text, and every page gets a skip link, landmarks and visible keyboard focus.
  link: What every page includes -> https://docs.micropage.sh/docs/concepts/accessibility

col:
  h3: Is it open source?
  p: No.

/// section align:center
icon: bi bi-chat-dots
h2: Still have a question?
p: Drop a line. I read every message.
button: Contact -> /contact

[Product -> /product]
meta:
  title: Micropage facts: features, limits and prices
  description: A hosted static site builder where each site is a plain-text .page file. Forms, newsletter, posts, custom domains, CLI and MCP server. Plans and limits.
  og_type: website

/// section
icon: bi bi-card-checklist
h1: Micropage product facts
p: Micropage is a hosted website builder. Each site is one plain-text .page file, written by hand, by the editor's AI tab, or by your own AI agent. Micropage compiles it to static HTML with working forms and hosts it over HTTPS on a micropage.sh subdomain or your own domain.
small: Prices in US dollars.
button: Start free -> https://app.micropage.sh
btn-outline: Compare plans -> /pricing

/// section
h2: At a glance

col:
  h3: Product type
  p: Hosted static site builder and host, with a web editor, a CLI and an MCP server. Not a visual drag-and-drop builder, not a CMS with a database, not a frontend framework.
  h3: Who it is for
  p: Developers, indie makers and small businesses who want a landing page, a multi-page site or a blog they can keep as a text file in git, and edit with an AI agent.
  h3: Source format
  p: The .page format is a closed, line-oriented markup. One element per line, no nesting, no arbitrary CSS. Raw HTML only inside a /// html block. Posts are Markdown files with front matter.

col:
  h3: Output
  p: Static HTML with one first-party stylesheet of 8 to 12 KB gzipped, self-hosted fonts and almost no JavaScript. Sitemap, robots.txt, per-page titles, descriptions and Open Graph tags are generated. Dark mode follows the visitor's OS.
  h3: Hosting
  p: Served from Cloudflare's network over HTTPS. Every publish is a numbered build that can be rolled back. Pro and Pro+ can download any build as a .zip and host it anywhere.
  h3: Price
  p: Free for one site on a micropage.sh subdomain, no card. Pro $6 a month or $49 a year. Pro+ $12 a month or $98 a year. Prices exclude VAT and sales tax; Paddle, the merchant of record, adds the tax for your country at checkout.

/// section
h2: Features and which plan has them

/// html
<style>
.mp-facts{width:100%;border-collapse:collapse;font-size:.9rem;line-height:1.4;margin:0 0 1.25rem}
.mp-facts-wrap{overflow-x:auto}
.mp-facts th,.mp-facts td{border:1px solid var(--bs-border-color);padding:.5rem .6rem;vertical-align:top;text-align:left;color:var(--bs-body-color)}
.mp-facts thead th{background:var(--bs-secondary-bg);color:var(--bs-heading-color)}
.mp-facts tbody th{font-weight:600;color:var(--bs-heading-color)}
</style>
<div class="mp-facts-wrap" tabindex="0">
<table class="mp-facts">
  <caption class="visually-hidden">Micropage features and the plans that include them</caption>
  <thead>
    <tr><th scope="col">Feature</th><th scope="col">What it does</th><th scope="col">Plans</th></tr>
  </thead>
  <tbody>
    <tr><th scope="row">Web editor</th><td>Markup on the left, live preview on the right.</td><td>All</td></tr>
    <tr><th scope="row">AI tab</th><td>Generates or edits the .page markup from a prompt. Credits refill monthly; more on paid plans.</td><td>All</td></tr>
    <tr><th scope="row">Multi-page sites</th><td>Pages are blocks in the file, linked by a nav block.</td><td>All</td></tr>
    <tr><th scope="row">Forms</th><td>A form is a few lines of markup. Submissions are stored per project, no backend needed. Cloudflare Turnstile and a spam filter keep bots out.</td><td>All. Per project, per month: 100 on Free, 1,000 on Pro, 10,000 on Pro+</td></tr>
    <tr><th scope="row">Posts</th><td>Markdown posts published at /content with an RSS feed.</td><td>All</td></tr>
    <tr><th scope="row">Newsletter</th><td>Any form can collect subscribers. Broadcasts go out by email with a delivery report.</td><td>Subscribers on all plans. Sending on Pro and Pro+</td></tr>
    <tr><th scope="row">Custom domain</th><td>One CNAME to cname.micropage.sh; the certificate is issued and renewed for you. Subdomains such as www only; redirect the bare domain to www at your DNS provider.</td><td>Pro, Pro+</td></tr>
    <tr><th scope="row">CLI</th><td>brew tap micropage-sh/tap &amp;&amp; brew install micropage, or npm install -g @micropage-sh/cli. Keep the .page file in your repo and publish from the terminal.</td><td>Pro, Pro+</td></tr>
    <tr><th scope="row">MCP server</th><td>Lets Claude, Cursor, VS Code and other MCP clients create, edit and publish pages and posts. Local (npm @micropage-sh/mcp) or hosted with OAuth. Sending email and deleting projects are off by default.</td><td>Pro, Pro+</td></tr>
    <tr><th scope="row">Zip export</th><td>Download any build as plain HTML, CSS and fonts.</td><td>Pro, Pro+</td></tr>
    <tr><th scope="row">Submission CSV and email digest</th><td>Export submissions; a daily email of new ones.</td><td>Pro, Pro+</td></tr>
    <tr><th scope="row">No badge</th><td>Removes the Micropage badge from the site.</td><td>Pro, Pro+</td></tr>
    <tr><th scope="row">Webhooks and instant email</th><td>Each submission is posted to your URL and emailed as it arrives.</td><td>Pro+</td></tr>
    <tr><th scope="row">Deploy tokens</th><td>Publish from CI, for example GitHub Actions.</td><td>Pro+</td></tr>
    <tr><th scope="row">Priority build queue</th><td>Builds skip the shared queue.</td><td>Pro+</td></tr>
  </tbody>
</table>
</div>

/// section
h2: Limits

col:
  h3: Projects
  p: 1 on Free, 5 on Pro, 20 on Pro+. One project is one site.

col:
  h3: Storage
  p: Uploaded files: 25 MB per project on Free, 100 MB on Pro, 500 MB on Pro+.

col:
  h3: Build time
  p: On Pro+, a publish is live in about 10 seconds. On Free and Pro, builds wait about 3 minutes in a queue first, then go live within seconds.

/// section bg:muted
h2: What Micropage does not do

- No visual drag-and-drop canvas. You edit text, or prompt the AI tab.
- No online shop, checkout or payments.
- No user logins, databases or server-side code on your site.
- No bare (apex) domain hosting; use www or another subdomain.
- No pixel-perfect layouts or design systems. Use Framer, Webflow or a frontend stack for those.
- Not open source.

/// section
h2: Leaving

p: The .page source of every project is plain text, available in the editor on every plan and through the CLI on Pro. Pro and Pro+ download any build as a static .zip that works on any host. Accounts can be deleted from the editor, which takes every site offline and cancels the subscription.

/// section
h2: Compared with other tools

col:
  h3: Micropage vs Carrd
  p: Carrd is cheaper and visual. Micropage is a file you keep in git.
  link: Read the comparison -> /content/micropage-vs-carrd

col:
  h3: Micropage vs GitHub Pages
  p: GitHub Pages is free static hosting. Micropage adds forms and needs no generator.
  link: Read the comparison -> /content/micropage-vs-github-pages

/// section
h2: Company and contact

p: Micropage is built and run by Cosmin Stefaniga. Support and questions: hey@micropage.sh or the contact form.
link: Contact -> /contact
link: Docs -> https://docs.micropage.sh
link: For AI assistants: llms.txt -> /llms.txt

/// html
<script type="application/ld+json">
{"@context":"https://schema.org","@graph":[{"@type":"WebPage","@id":"https://micropage.sh/product/","url":"https://micropage.sh/product/","name":"Micropage product facts","inLanguage":"en","about":{"@id":"https://micropage.sh/#software"}},{"@type":"SoftwareApplication","@id":"https://micropage.sh/#software","name":"Micropage","url":"https://micropage.sh","applicationCategory":"DeveloperApplication","operatingSystem":"Web","description":"Hosted website builder. Each site is a plain-text .page file compiled to static HTML with built-in forms, on a micropage.sh subdomain or your own domain.","offers":[{"@type":"Offer","name":"Free","price":"0","priceCurrency":"USD"},{"@type":"Offer","name":"Pro","price":"6","priceCurrency":"USD","priceSpecification":{"@type":"UnitPriceSpecification","price":"6","priceCurrency":"USD","unitCode":"MON"}},{"@type":"Offer","name":"Pro+","price":"12","priceCurrency":"USD","priceSpecification":{"@type":"UnitPriceSpecification","price":"12","priceCurrency":"USD","unitCode":"MON"}}],"publisher":{"@id":"https://micropage.sh/#organization"}}]}
</script>
<div></div>

[Contact -> /contact]
meta:
  description: Contact the Micropage team — tell us what you're building or what's blocking you.

/// section
icon: bi bi-envelope-heart
h1: Contact
p: Tell me what you're building or what's blocking you. I read everything.

form: contact
input: Name*
input: Email*
text: Message
submit: Send

[Privacy -> /privacy]
meta:
  description: Privacy policy for Micropage — how we collect, use, and protect information across micropage.sh and customer sites.

/// section
icon: bi bi-shield-lock
h1: Privacy Policy
p: Last updated: October 5, 2026
p: This Privacy Policy describes how Micropage ("Micropage", "we", "us", "our") collects, uses, discloses, and protects information when you use our websites, command-line tools, and hosted services related to micropage.sh (including subdomains such as app.micropage.sh and sites we host for customers on micropage.sh subdomains or custom domains), unless we tell you otherwise for a specific offering.

/// section
h2: Information we collect

col:
  h3: Account and authentication
  p: When you create or access an account (for example through the web app or CLI login), we collect identifiers and profile information needed to operate the service. This may include your email address, authentication provider identifiers (such as when you sign in with GitHub), and basic account metadata (for example plan or subscription status).

col:
  h3: Content you provide
  p: We store the projects, pages, assets, configuration, and other content you upload or sync so we can compile, preview, publish, and serve your sites. If you use forms on published pages, submission data is processed and stored as part of the service so you can retrieve it (for example in the product or via export features, depending on your plan).

col:
  h3: Billing and payments
  p: If you subscribe to a paid plan, Paddle processes your payment as our Merchant of Record. We typically receive limited billing information (for example the last four digits of a card, billing address elements, subscription status, and transaction references), not your full card number.

col:
  h3: Technical and usage data
  p: We collect diagnostic and usage information needed to run and secure the platform. This can include IP addresses, device and browser type, timestamps, request metadata, build and deploy logs, error reports, and aggregated usage metrics. We may use this data to prevent abuse, troubleshoot issues, and improve reliability and performance.

col:
  h3: Communications
  p: If you contact us (for example through a contact form or support channel), we keep the content of your message and related contact details so we can respond and maintain a record of the conversation where appropriate.

/// section
h2: How we use information
p: We use the information above to provide, maintain, and improve Micropage; authenticate users; process payments and administer plans; publish and serve customer sites; deliver form submissions and notifications where enabled; detect, investigate, and prevent fraud, abuse, and security incidents; communicate with you about the service; comply with law; and enforce our terms and policies.

/// section
h2: Legal bases (where applicable)
p: Depending on your region, we rely on appropriate legal bases such as performing our contract with you, pursuing legitimate interests that are not overridden by your rights (for example securing the platform and understanding aggregate usage), complying with legal obligations, and, where required, obtaining your consent (for example for certain cookies or marketing communications, if offered).

/// section
h2: How we share information
p: We share information with service providers who help us operate Micropage (for example hosting, infrastructure, bot and abuse protection, email delivery, analytics, payment processing, and customer support tools). They are permitted to use your information only on our instructions and where necessary to provide their services to us.
p: We may disclose information if we believe in good faith that disclosure is required by law, legal process, or governmental request; to protect the rights, property, or safety of Micropage, our users, or the public; or in connection with a merger, acquisition, financing, or sale of assets, subject to appropriate safeguards.

/// section
h2: Marketing site analytics
p: On some Micropage-controlled marketing or documentation pages, we may use privacy-oriented analytics (for example Plausible) to understand aggregate traffic. Such tools are configured to reduce personal data collection compared with many ad-tech platforms. For details, see the documentation or notices presented alongside those pages.

/// section
h2: Customer sites and end users
p: When you publish a site with Micropage, you decide what data you collect from your visitors (for example through forms). In that relationship, you are typically the controller of visitor data and we process it on your behalf to provide hosting and related features. You are responsible for your own privacy notices, consents, and compliance obligations for your site's visitors.

/// section
h2: Form spam protection
p: Forms on sites we host are protected by Cloudflare Turnstile, a bot-detection service from Cloudflare, Inc. When a visitor opens a page with a form, their browser loads Turnstile from challenges.cloudflare.com, which processes signals such as the visitor's IP address, TLS fingerprint, and browser user agent to tell people from automated traffic. Occasionally Turnstile may ask the visitor to complete a short check. Cloudflare processes these signals on our behalf to detect and block bots, and may also use them under its own legitimate interests to improve Turnstile's bot detection. See Cloudflare's Turnstile privacy policy: https://www.cloudflare.com/turnstile-privacy-policy/
p: We also check the content of form submissions automatically for common spam patterns, such as known bulk-marketing phrases or suspicious links. Submissions that look like spam are kept in a separate Spam view for the site owner and do not trigger notifications or newsletter sign-ups. Nothing is deleted automatically, and the site owner can move any submission back to their inbox. We do this to protect our customers and the platform from abuse.

/// section
h2: Data retention
p: We retain information for as long as your account is active and as needed to provide the service. We may retain certain records after closure where required for legitimate purposes such as legal compliance, dispute resolution, security, and backup integrity, then delete or de-identify them when no longer needed.

/// section
h2: Security
p: We implement technical and organizational measures designed to protect information against unauthorized access, loss, or alteration. No method of transmission or storage is completely secure; we encourage you to use strong authentication and protect your account credentials.

/// section
h2: International transfers
p: Micropage may be operated using infrastructure and subprocessors in multiple countries. Where personal data is transferred across borders, we use appropriate safeguards consistent with applicable law (for example contractual clauses or adequacy decisions).

/// section
h2: Your choices and rights
p: Depending on where you live, you may have rights to access, correct, delete, or export personal information; to object to or restrict certain processing; to withdraw consent where processing is consent-based; and to lodge a complaint with a supervisory authority. You can manage some information directly in the web app or by contacting us. We will respond consistent with applicable law.

/// section
h2: Children
p: Micropage is not directed to children under 16 (or the minimum age required in your jurisdiction), and we do not knowingly collect personal information from them. If you believe we have collected information from a child, please contact us and we will take appropriate steps.

/// section
h2: Changes to this policy
p: We may update this Privacy Policy from time to time. We will post the revised version on this page and update the "Last updated" date. Where changes are material, we will provide additional notice as required by law (for example by email or in-product message).

/// section
icon: bi bi-envelope
h2: Contact
p: For privacy-related requests or questions about this policy, email hey@micropage.sh or use the Contact page on this site.

[Terms -> /terms]
meta:
  description: Terms of Service for Micropage — the rules for using micropage.sh, the web editor, the CLI, the MCP server, and the sites we host for you.

/// section
icon: bi bi-file-earmark-text
h1: Terms of Service
p: Last updated: 5 October 2026
p: These terms apply when you use micropage.sh, the web editor at app.micropage.sh, the micropage command-line tool, the Micropage MCP server (mcp.micropage.sh and the npm package @micropage-sh/mcp), and the hosting of sites we publish for you on micropage.sh subdomains or on your own domain. Together we call these "Micropage" or "the service". By creating an account or using the service, you agree to these terms.

/// section
h2: Who we are
p: Micropage is run by Ștefănigă D. Cosmin-Lucian PFA (persoană fizică autorizată), CUI 34668358, trade register F11/350/2015, Str. Dacilor nr. 11, 325400 Caransebeș, Caraș-Severin, Romania ("we", "us"). Contact: hey@micropage.sh
p: How we handle personal data is described in our Privacy Policy.
link: Privacy Policy -> /privacy

/// section
h2: Accounts
p: You need an account to create and publish projects. You must be at least 16 years old to have one. If you use Micropage for a company or organization, you confirm that you can accept these terms on its behalf.
p: Keep your sign-in details, CLI logins, deploy tokens, and MCP credentials private. You are responsible for what happens under your account, including actions taken by an AI agent or CI job you have given access. Tell us promptly if you think someone else has access.

/// section
h2: Plans and billing
p: Micropage has a Free plan and two paid plans, Pro and Pro+. What each plan includes and costs is listed on the Pricing page. Free sites show a Micropage badge.
link: Pricing -> /pricing
p: Paid plans are sold through Paddle, which acts as our Merchant of Record. Paddle is the seller of record for your purchase: it takes the payment, charges any sales tax or VAT, and issues the invoice. Paddle's buyer terms apply to the payment itself.
p: Subscriptions are billed monthly or yearly and renew automatically until you cancel. You can cancel at any time from your account. Cancellation takes effect at the end of the period you have already paid for, and your paid features keep working until then.
p: Refunds: if you are not happy with a new subscription, ask for a refund within 14 days of its first payment and we will refund it in full through Paddle. Renewals are not refunded, except where the law requires it.
p: We may change prices. A new price applies only from your next renewal, and we will tell you before that renewal.

/// section
h2: Your content
p: Your content is yours: the .page files, posts, images and other files you upload, the sites built from them, and the form submissions and subscriber lists your sites collect. We claim no ownership of it.
p: To run the service, you give us a worldwide, non-exclusive, royalty-free licence to store, copy, compile, build, host, cache, display and serve your content, and to send it to the providers that help us run Micropage. We use this licence only to provide the service to you and the visitors of your sites. It ends when you delete the content, except for copies held for a short time in backups and caches.
p: You confirm that you have the rights to everything you publish, and that publishing it does not break these terms or the law.

/// section
h2: Acceptable use
p: Do not use Micropage to publish or send:
p: phishing pages, or forms that collect passwords, payment card details or other credentials under false pretences;
p: malware, or links meant to deliver it;
p: spam, including newsletters sent to people who did not opt in to receive them;
p: illegal content, or content that infringes someone else's copyright, trademark or other rights;
p: content that impersonates another person, company or organization.
p: Do not abuse the infrastructure: no attempts to break into the service or other accounts, no getting around plan limits, no load testing or scraping that degrades the service, and no use of hosted sites as a file host or proxy unrelated to the site.
p: If we believe content or an account breaks these rules, we may remove the content, take a site offline, or suspend the account. Where the risk to others is low, we will tell you first and give you a chance to fix it. For phishing, malware and similar abuse, we act first and tell you afterwards.
p: To report abuse on a site we host, email hey@micropage.sh with the link.

/// section
h2: Your site's visitors and forms
p: When your site collects data from its visitors, through forms, newsletter sign-ups or anything you add yourself, you decide what is collected and why. You are the controller of that data, and we process it on your behalf to provide the service. You are responsible for telling your visitors how you use their data, for any consent you need, and for answering their requests. Our Privacy Policy explains how we process it.
link: Privacy Policy -> /privacy

/// section
h2: Domains
p: Subdomains of micropage.sh belong to us. We lend one to your project while it exists. When a project is deleted, its subdomain may be given to someone else. We may refuse or change a subdomain that is misleading, impersonates someone, or is reserved for our own use.
p: A custom domain you connect must be one you own or are allowed to use. You keep control of its DNS. When you stop using Micropage for that domain, remove the DNS record that points it to us.

/// section
h2: AI features
p: The editor and the MCP server can generate or change markup with AI models run by third-party providers. AI output can be wrong, incomplete, or similar to someone else's work. Review it before you publish; what you publish is your responsibility.
p: AI credits are included with each plan and refill monthly. They have no cash value, cannot be transferred or exchanged for money, and are not refunded when unused.

/// section
h2: Availability
p: We work to keep Micropage and the sites we host running, but we offer it on a best-effort basis with no service level agreement. The service may be slow or unavailable at times, for maintenance, because of a provider we depend on, or for reasons we did not foresee. Builds on the Free and Pro plans wait in a lower-priority queue.
p: Keep your own copy of anything you cannot afford to lose.

/// section
h2: Leaving
p: You can take your site with you at any time. The .page source of every project is available in the editor, and Pro users can also pull it with the CLI. On Pro and Pro+, you can download any build as a static .zip and host it anywhere.
p: Deleting a project takes its hosted site offline. This cannot be undone. To close your account, choose Delete account from the account menu in the editor. This deletes all your projects and sites and cancels any subscription immediately.

/// section
h2: Termination
p: You can stop using Micropage at any time by cancelling your subscription and deleting your projects.
p: We may suspend or close your account if you seriously or repeatedly break these terms, if we are required to by law, or if your use puts other users or the service at risk. Where we can, we will tell you why and give you time to export your content first.
p: If we decide to shut Micropage down, we will tell you at least 30 days in advance, so you can export your sites, and we will refund any fees you prepaid for the time after the shutdown.

/// section
h2: Disclaimers and limitation of liability
p: Micropage is provided as it is and as available. To the extent the law allows, we make no promises that it will meet your needs, be free of errors, or be uninterrupted.
p: To the extent the law allows, we are not liable for indirect or consequential loss, such as lost profits, revenue, data or business opportunities. Our total liability for any claim relating to Micropage is limited to the fees you paid us in the 12 months before the claim arose.
p: These limits do not apply where the law does not allow them, including liability for intent or gross negligence, and they do not reduce the rights you have as a consumer.

/// section
h2: Changes to these terms
p: We may update these terms. The date at the top shows the latest version. Before a material change applies, we will tell you by email or in the app. If you do not agree with the change, you can cancel before it applies; continuing to use Micropage after that means you accept it.

/// section
h2: Governing law
p: These terms are governed by Romanian law, and disputes go to the competent courts of Romania. If you use Micropage as a consumer, you keep the protection of the mandatory laws of the country where you live, and you can bring a claim in the courts there.

/// section
icon: bi bi-envelope
h2: Contact
p: Questions about these terms: hey@micropage.sh, or use the Contact page.
link: Contact -> /contact

[Blog -> /blog]
meta:
  description: The Micropage blog lives at /content.
  noindex: true

/// section align:center
h1: Blog
p: Guides, how-tos and comparisons for building websites from a .page file.
button: Go to the blog -> /content

[Showcase -> /showcase]
meta:
  title: Real sites, with the source file for each
  description: Real sites built with Micropage — browse the live page and inspect the source for each.

/// section
icon: bi bi-grid-3x3-gap
h1: Built with Micropage
p: Real sites running on Micropage. Click Source to see the file behind each one.

/// section

col:
  h3: usewit.app
  p: Wit, a free, open-source editor for books and scripts, with live page previews and PDF export.
  img: alt: usewit.app homepage <- showcase-usewit-app.png
  link: Website -> https://www.usewit.app
  link: Source <- showcase-usewit-app.txt

col:
  h3: lantern.travel
  p: A simpler way to let people know you're safe while traveling.
  img: alt: lantern.travel homepage <- showcase-lantern-travel.png
  link: Website -> https://www.lantern.travel
  link: Source <- showcase-lantern-travel.txt

col:
  h3: maproll.io
  p: Choropleth maps from a clean URL or an AI prompt. SVG, PNG, embeddable.
  img: alt: maproll.io homepage <- showcase-maproll-io.png
  link: Website -> https://maproll.io
  link: Source <- showcase-maproll-io.txt

col:
  h3: micropage.sh
  p: This site: home, pricing, tour, FAQ and showcase from one file.
  img: alt: micropage.sh homepage <- showcase-micropage-sh.png
  link: Website -> https://micropage.sh
  link: Source <- showcase-micropage-sh.txt

col:
  h3: mpaenergy.fr
  p: Énergie verte: HVAC, pompes à chaleur et photovoltaïque.
  img: alt: mpaenergy.fr homepage <- showcase-mpaenergy-fr.png
  link: Website -> https://www.mpaenergy.fr
  link: Source <- showcase-mpaenergy-fr.txt

col:
  h3: hungry-bits.com
  p: Web agency building landing pages and apps for growing businesses.
  img: alt: hungry-bits.com homepage <- showcase-hungry-bits-com.png
  link: Website -> https://www.hungry-bits.com
  link: Source <- showcase-hungry-bits-com.txt

col:
  h3: maralbosoftware.com
  p: Mobile and web development for ambitious startups.
  img: alt: maralbosoftware.com homepage <- showcase-maralbosoftware-com.png
  link: Website -> https://www.maralbosoftware.com
  link: Source <- showcase-maralbosoftware-com.txt

col:
  h3: capitalpanda.xyz
  p: A world-capitals quiz — three difficulty modes and per-question timing. Country shapes from maproll.io.
  img: alt: capitalpanda.xyz homepage <- showcase-capitalpanda-xyz.png
  link: Website -> https://www.capitalpanda.xyz
  link: Source <- showcase-capitalpanda-xyz.txt

col:
  h3: chordbench.xyz
  p: A free, no-signup guitar chord library and strum-along player for adult beginners.
  img: alt: chordbench.xyz homepage <- showcase-chordbench-xyz.png
  link: Website -> https://www.chordbench.xyz
  link: Source <- showcase-chordbench-xyz.txt

col:
  h3: seedling.page
  p: A free, no-signup maze generator for kids — printable on A4 or US Letter.
  img: alt: seedling.page homepage <- showcase-seedling-page.png
  link: Website -> https://www.seedling.page
  link: Source <- showcase-seedling-page.txt

/// html
<style>
/* Showcase grid: cap at 4 columns on desktop, wrapping to new rows. */
.mp-section-row > .mp-column{
  flex:0 0 auto;
  width:25%;
}
@media (max-width: 991.98px){
  .mp-section-row > .mp-column{ width:50%; }
}
@media (max-width: 575.98px){
  .mp-section-row > .mp-column{ width:100%; }
}
</style>

/// section bg:muted align:center
h3: Want yours here?
p: Build with Micropage and ping us.
button: Start free -> https://app.micropage.sh
btn-secondary: Contact -> /contact