Who lazysite is for
From a one-file portfolio to an AI-published content business — and built for the human/AI partnership in between.
lazysite suits anyone who wants a fast, file-based site without the weight of a database or a CMS to maintain. It is especially at home where an AI agent does the work — describe what you want, and it is published. You stay in control of every file.
Who it's for
Students & junior developers
A professional portfolio in minutes - free, fast, and yours - to land an internship or showcase coursework. No build tooling to learn first.
Engineers & sysadmins
A personal blog or project documentation with no database to run and no CMS to patch. It is just a CGI script and a tree of Markdown.
Content automators
Generating Markdown from scripts or an LLM? lazysite is the drop-in renderer - write files, they are served, with feeds and an llms.txt for free.
Marketers & site designers
Using AI for rapid site development: spin up a site, restyle it from a gallery of themes, and iterate in minutes instead of sprints.
Publishers
Get content out the door quickly - and keep some of it private behind pay-per-read, so writing can earn as it is read.
Teams, intranets & small groups
An internal knowledge base, a team intranet, or shared information for a club, group or household - private by default, with per-user access and nothing to administer.
Community websites
For a club, association, neighbourhood or user group: a shared site that is cheap to run and easy for volunteers to keep current. Hand contributors scoped, revocable access - or let an AI agent maintain it - with no database or hosting bills to worry about.
Catalogue & directory sites
Build a product catalogue, directory or listing from internal JSON data files - lazysite reads them and renders the pages, with no database server to run. (The comparison and feature tables on this very site work exactly that way.)
What you can do with it
Publish from your phone. Describe an article to Claude. It writes the Markdown and publishes it — live instantly, or held for review first if you would rather approve it. No laptop, no dashboard, no deploy.
Sell what you write. Put a page behind pay-per-read with the built-in x402 payment support. Private, paid content sits alongside your free pages and uses the same workflow.
Let the docs write themselves. Pull pages straight from a code repository with .url files, so documentation always reflects the current version without copying it twice.
Built for a human/AI partnership
lazysite treats AI publishing as a first-class use case, not a bolt-on. An agent edits content over WebDAV, a control API, or the Model Context Protocol — and it goes through exactly the same rules a person does. There is no privileged back door for automation: the agent inherits a partner's capabilities and per-file permissions, every change is logged, and you decide how much it may touch.
That means you can hand an assistant a narrow, time-boxed grant — "draft and publish to the blog, nothing else, expires Friday" — and trust the core to hold that line.
You stay in control
Fine-grained controls let you decide exactly who — human or AI — can do what:
- Lock files so no one else can alter them while you work — a lock taken anywhere is respected everywhere.
- Per-user capabilities — grant editing, theming, configuration or user-creation independently, so each account does only what it should.
- Per-file access control — set an owner with read and write lists; access only ever narrows, never widens.
- Account & token expiries — time-box a contributor or a partner; access fails closed when it lapses.
- Delegation & sub-users — let a partner mint scoped sub-accounts, but never grant more authority than they hold themselves.
- An audit trail — an append-only record of who changed what, when, from where, and the outcome.
See the full feature list, how lazysite compares, or read about lazysite.