Spaces

Open one. Get to work.

Sales has its own. Support has its own. Routes, revenue, code, notes, the messy thing nobody built software for — each gets its own. Browse what's installed, add what isn't, and switch between them like rooms in a house.

Construct Spaces marketplace and launcher grid
Screenshot needed

The Spaces marketplace inside Construct. Category sidebar (Productivity, Business, Finance, etc.), grid of Space cards with icon, name, version, short description, and an Install button per card. Mix of installed and not-yet-installed Spaces.

/shots/spaces-launcher.png

Anatomy

What a Space is made of.

Four layers — the host chrome you sign in to, the subspaces rail, the toolbar, and the content surface. Every Space is a stack of these, tuned to its workflow.

Exploded isometric diagram showing the four layers of a Space
Screenshot needed

Exploded isometric diagram of a Space, top to bottom: space content (boards / cards), space toolbar (Create board action), space subspaces (rail of Space icons), host chrome (window controls + sidebar). Labeled callouts with thin dotted lines connecting each layer to its name. Light cream background, accent-red highlights.

/shots/anatomy-of-a-space.png
Host chromeThe window the OS gives every Space — sign-in, sidebar, theme, account.
SubspacesRail of focused views inside the Space — boards, queues, settings, automations.
ToolbarThe actions that belong to the open subspace. Create, run, approve.
ContentThe actual work surface. Boards, queues, dashboards, editors — whatever the workflow needs.

Underneath

Every Space inherits from the system.

Identity, memory, models, tools, permissions — handled once at the OS level. Spaces compose against them instead of reinventing them.

Its own interface

A real UI for the job — boards, queues, dashboards, editors. Whatever the work needs.

Its own Operator

An AI that knows this Space, its data, its actions. Not a generic chatbot dropped on top.

Its own memory

Decisions, files, recent state, preferences — kept inside the Space, carried turn to turn.

Shared identity & files

Sign in once, access lives at the system level. Spaces inherit from the OS, not the other way around.

Permissions you control

Read-only, run-tools, auto-execute — Spaces declare what they need, you decide what to grant.

Distribution, three ways

Public on the marketplace, private to your org, or scoped to a single project. Same SDK either way.

Marketplace

If a workflow deserves software, it can be a Space.

The marketplace expands the system over time. Install the ones you need, build the ones nobody made yet.

CRMPatient RecordsContract ReviewFloor PlansTrading DashboardLesson BuilderInventoryPayrollHelpdeskHabitsNotesDocsInvoicingSubscriptionsTime trackingJournalCalendarDesignVideoYour workflow