Skip to main content

Welcome to Flexweg documentation

Flexweg is a hosting platform for static websites. You upload a folder of HTML, CSS, JavaScript, images, fonts and videos — we serve them at a URL of your choice, for free, with global delivery and sensible defaults built-in.

This documentation walks you through everything: your first page, connecting an AI assistant to your site, real-world tutorials (documentation site, blog), the full REST API, and more.

What you can build on Flexweg​

  • Landing pages and marketing sites
  • Documentation sites — we use Flexweg to host these very docs
  • Blogs with a visual editor — see the Decap CMS tutorial
  • Portfolios and agency sites
  • Product demos and prototypes
  • One-shot HTML pages for AI agents — with a public endpoint that needs no account

Any static output works: handwritten HTML, a Docusaurus site (what you're reading right now), an Eleventy blog, Hugo, Astro, Next.js exports, Vite apps — if it builds to a folder of static files, Flexweg hosts it.

Your imagination is the only limit. Every list above is just a starting point — Flexweg serves any valid HTML/CSS/JS, so whatever you can dream up (or whatever an AI can dream up with you), you can ship here.

Why static​

Static sites are HTML, CSS and JavaScript files served as-is from a CDN. There's no PHP, no Node.js, no database running on your behalf. That simple model buys you a lot:

  • Speed — a pre-rendered page served from a CDN beats any dynamic backend for time-to-first-paint.
  • Reliability — no database to go down, no PHP runtime to crash, no memory leaks. The dreaded 500 error simply doesn't exist on a static site: there's no code running at request time that could fail. What's there is there, always.
  • Zero maintenance, no DevOps required — nothing to patch, no runtime to upgrade, no security advisory at 3am about a framework CVE. You don't need a sysadmin, a DevOps engineer, or a Kubernetes cluster. Your site is a folder of files — it just stays online.
  • Security — no server-side code means no server-side vulnerabilities. The attack surface shrinks to your frontend.
  • Cost — no compute to provision. Free-tier plans cover real projects.
  • Portability — your site is a folder. Move it anywhere, version it in git, deploy it via any CI.
  • Lighter on the planet — every request to a traditional website spins up a PHP worker, queries a database, re-renders the same HTML, and burns CPU cycles doing it. A static site is already rendered: edge nodes serve it from cache, usually without touching an origin server at all. Fewer CPU cycles, fewer kWh, fewer emissions — hosting static is, page for page, one of the most energy-efficient choices you can make on the web.

"Static" doesn't mean "no dynamic data". You can still read from and write to external services — APIs, databases, auth providers — from the browser. See Connect to external databases for the patterns.

Static is the future — especially now that AI writes it​

For twenty years, the case for static felt incomplete: yes, static is faster and cheaper, but somebody had to write the HTML. Large sites meant a CMS, which meant a runtime, which meant servers. The trade-off ran the other way.

That trade-off has evaporated. Modern AI models — Claude, GPT, Gemini — generate production-quality HTML, CSS and JavaScript in seconds. The natural pipeline now looks like this:

Describe what you want → AI produces HTML → Flexweg hosts it

No runtime, no SSR cluster, no CMS to operate. An AI drafts the page, you publish it as a static file, the edge serves it. When you need to change it, the AI reads the existing HTML, edits it, and re-uploads it — which is exactly what our MCP server exposes to Claude, Cursor, ChatGPT, Gemini, VS Code and other AI clients. Flexweg is purpose-built for this flow:

Static sites were always the right engineering answer. With AI in the loop, they're also the right productivity answer — and the one that scales to planet-friendly hosting.

What Flexweg gives you on top​

  • A URL immediately — a blank site is provisioned at https://<random>.flexweg.com the moment you sign up. Customize the subdomain or plug in your own domain.
  • A file explorer in your browser — upload, edit, preview and publish files without touching a terminal. See Publish your first page.
  • A REST API for every operation — list, read, upload, rename and delete files; manage folders, videos and forms. See the API reference.
  • A Model Context Protocol (MCP) server — plug Claude, Cursor, ChatGPT, Gemini, VS Code directly into your site. Your AI reads and writes files for you. See MCP integration.
  • Built-in forms — contact, newsletter, survey. Create in the dashboard, embed anywhere on your account, get emails and a searchable inbox. See Forms on your site.
  • Transparent AI pricing — use your own Anthropic/OpenAI/Google API key (no markup), buy prepaid tokens, or just use a free AI tool and paste the HTML in. See Build your site with AI.

Where to start​

Learn the basics​

New to Flexweg or to static hosting? Start with the Core concepts:

  1. How sites work on Flexweg — how URLs map to your files, what file types are supported.
  2. Publish your first page — put a Hello World online in under 10 minutes, no terminal needed.
  3. Share styles across pages — move CSS into a single main.css, reuse it everywhere.
  4. Build your site with AI — let Claude / Gemini / ChatGPT generate your pages; three ways to pay (or not pay) for AI.

Build something real​

Follow a step-by-step tutorial from a blank machine to a live site:

Connect AI to your site​

Let an AI assistant manage your files directly, without copy-paste:

Advanced topics​

Go beyond static hosting:

  • Connect to external databases — Supabase, Firebase, PocketBase, Airtable, serverless proxies — five patterns to read and write real data.
  • Forms on your site — contact forms, newsletter signups, surveys — all built-in, no third-party service.

API reference​

For developers automating Flexweg from CI, scripts, or custom integrations:

Need help?​