Skip to content
The Stacklumen platform is in private alphaSee the products

Design the site.
Ship the site.

Terminal is the visual site builder inside Stacklumen: a real canvas over real HTML and CSS, breakpoint layers you author rather than preview, and a publish button that puts the result on a live address. Staging is free on every plan; a site on its own domain takes a site plan.

Open Terminal Create an account
Status
Alpha
Lives at
stacklumen.com/terminal
Editor
Visual canvas + code view
Breakpoints
4 authored layers
Publishes to
A staging link, then your domain
Custom domains
TLS issued and renewed
Agent door
MCP, 52 tools
Pricing
Staging free · Site plans from $18/mo

Terminal, the Stacklumen site builder, in its light frame: one bar with the site and page, four breakpoint layers, zoom, Preview and Publish; the rail beside the layers tree; a client page on the canvas; and the inspector with its state tray and property groups. A short demo plays: the cursor opens Typography, drags the heading from 46 to 58 pixels, retypes its last words on the canvas, then walks the page through Tablet and Phone and back.

The designer, drawn to the editor's own proportions. The layers tree and the canvas select each other; the inspector reads back whatever is selected.

What you draw is what ships. One document, canvas to visitor.

The editor holds an ordinary document: tags, classes and a stylesheet. Publishing serialises exactly that and preview uses the same serialiser, so it cannot lie. No runtime and no framework sit between what you drew and what a visitor loads.

Selection

Element
h1
Class
.cs-split__title
Font size
46px
Weight
660
Line height
1.06

Stylesheet

.cs-split__title { font-size: 46px; font-weight: 660; line-height: 1.06; }

A screen in the hub, not a second app

One Stacklumen sign-in and one workspace with the dashboard, the CRM and your clients. Sites belong to clients, and the work lands on the same activity trail.

Everything autosaves

Closing the tab costs nothing, and the live site does not move until you publish again.

Build the page. Then style the class.

Start from a page and its tree. Drop in Blocks (Navbar, Hero, Feature grid, Pricing, Contact form, Footer) or single elements from Insert. Select anything and the inspector reads it back; styling writes to a class, so every element that carries it follows.

The Terminal designer in its light frame. A short demo plays: the cursor drags the Feature grid block from Insert onto a client page, selects the first card, retypes its title, gives the card class a brand border on its Hover state, sets the class to slide up when scrolled into view, and previews it. The inspector beside the drawing is real: its state, border colour, trigger, animation and duration controls change the drawing.

Inspector div

div › .cs-card 3 elements

  • Borders···

    Colour

Eight keys, three rows

Where you are and what goes in it (Insert, Pages, Layers), the content (Collections, Assets, Baselumen), and how it looks (Styles, Apps). Clicking an open panel's key gives the stage its width back.

Style, Interact, Settings

Hover, focus and active are layers over the base. Interactions fire on click, hover, load or scroll into view: animate, show, hide, toggle, toggle a class, scroll to, or go to a URL. Settings holds attributes, the tag and bindings.

Breakpoints are layers. Not previews.

Desktop is the base. Laptop, Tablet and Phone are layers you author on, and each stores only the fields you changed, so a later desktop edit still reaches everything a narrower layer has not pinned. The cascade runs downward, the way a max-width media query does.

The Terminal designer's breakpoint layers, working. Choose Desktop, Laptop, Tablet or Phone to see the artboard at that width and the page reflow, and change the heading size on any layer: narrower layers inherit a wider layer's size until you change it there.

Inspector h1

46px

Set on .cs-split__title

Desktop: the 1200px base. Every other width inherits from it.

Find the width, then fix it there

Switch layers from the toolbar or the number keys, or sweep the scrubber to find the width something breaks at. An edit at a narrow layer never travels back up. Phone is authored at 390 and published to 480.

The site keeps taking input. Collections, forms and assets.

All three read and write the same document the canvas edits. Bind the parts of one card to a collection, repeat it, and the content takes the shape you drew.

The Terminal designer with a Projects collection. A short demo plays: an item is added to the collection and named Harbor Station, and it appears in the list of projects on the client's Work page; then the list is sorted by year, newest first, limited to two, and given a Load more button, then page links. The Collections panel beside the drawing is real: its sort, direction, limit and pagination controls change the list.

Collections 1 collection

Showing 3 of 3 matching · 3 items in Projects. Drafts are never shown.

Sort by
Direction
6
Pagination

A page per item

Mark a page as a collection's detail template and publishing renders one page per item at its own slug, sitemapped and rollable.

Forms that answer

Submissions land on the site's Form submissions screen, paginated and exportable. Contact and Newsletter blocks ship with a honeypot; the endpoint authenticates by site.

Assets per site

Uploads belong to the site, not the workspace, so one client's images never appear in another client's designer.

Publish a snapshot. Roll it back whenever.

Publishing renders every page to a standalone document and keeps the set as one deployment. The live site serves those bytes and nothing else, so the draft can change all afternoon and the site does not move until you publish again.

Live on a staging link

Every publish is live on a staging address at once, with internal links kept inside it, so a staged site behaves like the real one. When it is ready, connect its own domain: one TXT record proves it is yours, the DNS points it here, and the certificate is issued for you.

Nothing is one-way

A rollback republishes an older snapshot as a new deployment, so it can itself be rolled back. Unpublish takes a site offline without deleting it; Restore brings it back.

In every page, and after

  • Titles, meta descriptions and share images per page.
  • Canonical URLs for the address that serves the page.
  • A frozen sitemap, robots.txt, redirects and a 404 with a real 404 status.
  • First-party page views in the designer, reported as a floor.

The editor, addressed over MCP.

An external agent works on a site through the same validated actions the canvas dispatches, into the same undo history and the same activity trail. It is the editor, addressed differently, not a second API that drifts from the first.

An agent working on a client's site over Terminal's MCP endpoint (52 tools). A short demo plays: it reads the home page, retypes the heading and recolours the button, and its request to publish is refused because the token lacks the publish scope; with a full-access token the publish succeeds, and a token limited to one site cannot read another client's site. The token controls beside the drawing are real.

Agent token

Reach
Scopes

design:read · design:write · collections:read

Tick what this token may do. Nothing ticked mints a full-access token.

Tokens you can account for

Minted by the workspace owner, optionally limited to one site, and scoped by function. Every write is attributed to its token, and the designer tells you when a token changes a document you have open.

Framework code, through your agent

The Frameworks panel briefs your agent on an Astro, React, Vite, Vue, Svelte or plain HTML project, and it builds the pages here. Writes the canvas could not produce are refused, not approximated.

Bring work in

Baselumen components import as ordinary elements, free templates and section libraries install from the marketplace today (paid checkout is coming), and Terminal Cloud mounts an app on a path.

Browse the marketplace

Where it fits

The screen in the Stacklumen Hub where sites get made, beside the clients, CRM and billing they belong to.

See the products

Get started

Sign in, create a site from the dashboard, design it and publish to the staging link. Share it with whoever needs to see it.

Open Terminal

Questions. The ones people actually ask.

Do I need to know how to code?

No. The canvas, the Blocks and the inspector are the whole workflow. If you do know CSS, a Custom CSS field and a code view are there when you want them.

What does it cost?

Terminal is on your agency's Stacklumen plan, the same one that covers the Hub and Baselumen: Free, Pro at $24/mo or Agency at $29.99/mo with 3 editor seats. Every site publishes to its free staging address on every plan. A site on its own domain takes a site plan: Basic at $18/mo, or CMS at $30/mo with 20 collections and the live Content API. App routes add $15/mo to a site. Everything is free during the private alpha. The pricing page has the detail.

Can another app read a site's content?

Yes. The Content API serves a site's CMS content with keys bound to that one site, so a key handed to a front end can read nothing else.

What does "alpha" mean here?

That there are rough edges and unfinished surface area, not that it is a demo. The designer, autosave, publishing, the CMS, form submissions and the agent door all run today, and our own engineering team ships client sites with it.

Can Stacklumen build the site for us?

Yes. Our engineering team builds client sites in Terminal today, and enterprise builds are delivered by our enterprise team until Terminal reaches general availability. At general availability, Terminal opens a marketplace of creators: choose an independent creator, or work with our internal development team.

Can I bring an existing site in?

Through your agent. The Frameworks tab (Astro, React, Vite, Vue, Svelte or vanilla) writes a brief for the agent you already use, with the MCP endpoint and the site’s id filled in; the agent reads the real project and builds it here through validated writes. The old Astro importer and pasted markup are gone. Saved components, the Baselumen library, marketplace libraries and templates still install.

Can an AI agent edit my site?

If you give it a token. The MCP endpoint offers 52 tools covering sites, pages, text, attributes, the stylesheet, components, collections, revisions, form submissions and publishing. Tokens are minted by the workspace owner, can be scoped to a single site, and every write is attributed to the token that made it.

Can I edit on a phone or a tablet?

No, deliberately. The designer needs at least 1100px of viewport rather than reflowing into a layout where a drag lands on the wrong element. Narrow layouts are designed on a wide screen, which is what the breakpoint layers are for.

Open it and draw something.

The fastest way to understand a builder is to put a section on a canvas and publish it. Terminal comes with your Stacklumen account, and every site stages free.

Open Terminal See pricing
Made inTerminal