BETA · OWN YOUR PRESENCE · NOT RENTED

Your website, your rules. Free, forever.

Your AI agent builds it, you write. Built on the shoulder of giants, free, open source.

Open source. Publishing works today. Private capture, connections and long-term AI memory are the next chapter.
A little room to writeThe Lanza writing workspace
Lanza’s rich-body editor showing an article with a clear title and writing area, with Format and Details available on demand.

The actual editor, with sample content. Your words get the space.Take the guided tour ↗

THE SYSTEM WE ARE BUILDING

Capture first. Write later.

Not every thought needs to become a post. We are building toward a private thinking space beneath the public website. These principles guide what comes next.

01 / CAPTURE

Start with a fragment.

The next chapter begins with notes, links, quotes and questions. Images and voice belong here too. No headline, polished argument or publishing date required.

02 / RETURN

Let ideas take their time.

A thought from six months ago might be exactly what you need today. We want related ideas to find their way back to you, with the original context intact.

03 / DEVELOP

An assistant, not your replacement.

AI should ask a useful question, find a contradiction, or connect two observations. Your judgment remains the point of the work.

04 / PRESERVE

Keep the path, not just the result.

Original notes, sources and revisions matter. Our direction is explicit provenance: distinguish what you supplied from what AI suggested and what you chose to keep.

05 / PUBLISH

Choose what becomes public.

The publishing beta already separates saving from going live. The future notebook must go further: sharing an article must never expose the private thinking beneath it.

06 / OWN

Build something that lasts.

Your domain, portable files and a history you control. After ten years, the aim is a connected body of thought—not another feed you cannot take with you.

AVAILABLE TODAY · THE PUBLISHING FOUNDATION

Your words. Your decision.

The thinking system grows from a working foundation: writing, editable pages, your own repository and deliberate publishing. Here is what you can use in the beta now.

01 / WITH YOUR AGENT

Describe the site.

Bring a brief, rough notes or a conversation. Your connected agent creates the structure, design and editable content fields.

02 / IN YOUR CMS

Make the words yours.

Write a post. Refine a landing-page headline. Replace an image. Open Details for the URL, search appearance and publishing settings.

03 / ON YOUR TERMS

Review, then go live.

Check the staged changes and preview. Publish sends them to the live branch, where Cloudflare builds the updated site.

A better role for AI

“Here is an argument I am developing. Ask me what is missing, point out contradictions, and help me edit. Keep your suggestions separate from my words.”

NOT EVERY TASK FITS IN A SIDEBAR

Small details. Plenty of space.

A better search description deserves more than a cramped input. Expand Details, work through the fields, then return to your writing. The document stays right where you left it.

Learn your way around ↗
The expanded Lanza Details panel with URL, summary, image and direct search appearance fields.
YOUR WORK, YOUR GROUND

Keep the house. Choose the doors.

Cloudflare is the land. GitHub is the house and its history. Lanza helps you organize it and choose what to open to the world. The private thinking space needs its own boundary; an unpublished file in a public repository is not private.

Explore the source ↗
  • The landYour site runs in your Cloudflare account, under your domain.
  • The house and its historyGitHub holds the source files and revisions. Repository access determines who can read them.
  • The doors you openYou decide what to publish. Private notebook storage is being designed separately from the public website.
GOOD QUESTIONS

The promise, and where we are.

Can I use Lanza today?

Yes. The beta provides writing, page editing, multilingual content and reviewed publishing on your own website. Private thought capture, a connected notebook and automatic resurfacing are planned work, not features available today.

Is an unpublished draft private?

Not necessarily. Saving to staging keeps it off the published site, but anyone with repository access can read the file. A public repository makes those files public. The planned notebook needs a separate private storage boundary.

Will AI write my thoughts for me?

That is not the goal. AI should organize, challenge, find connections and help edit. You decide what you believe and what you want to say. Long-term memory and proactive connections are not yet implemented.

Will my thinking be used to train AI?

Research or training licensing is only a possible future direction, with separate, explicit consent for selected material. Publishing a piece must not become permission to license private notes. Connected AI services have their own data terms.

What can I take with me?

Your existing site content, templates and settings are files in your GitHub repository, with Git history. You control your domain and hosting accounts. Portable notebook files and provenance are requirements for the next chapter.

Does Save publish my work?

No. Save writes website changes to staging. Publish sends all staged website changes to the live branch. Review them before publishing.

More human thinking. Not more AI content.

That is the work we want technology to make room for.