Solutions

Game studiosProduction, art and QA on one board.StartupsRoadmap, customers and research in one place.AgenciesClients, retainers and hours next to the work.OperationsRequests, assets and vendor renewals.

Platform

SurfacesPages, databases, views, dashboards, canvases and automations.Snoze AIReads the workspace with your permissions and writes back into it.TemplatesStart from a shape that fits, then change it.IntegrationsImport from old tools, sync with the ones you keep.

Support

Help centreSet up a first workspace in about twenty minutes.Talk to a humanA walkthrough using your own work.Desktop appmacOS and Windows, in progress.ChangelogWhat shipped this week.
PricingSign in

Platform

Six surfaces.
One set of records.

Learn all six in an afternoon. Change any of them later.

01Views

Four layouts,
one database.

Table, board, calendar and timeline are views over the same rows. Switching between them moves nothing and copies nothing.

  • Each view keeps its own filters, sort and permissions
  • Share one view without sharing the database
Workspace/Production board

Production board

Filter New
TableBoardCalendarTimeline6 records
NameStatusPriority
Player controller feel passIn productionCriticalAR
Boss arena blockoutIn productionHighKM
Save system migrationBacklogHighTL
Steam page copyBacklogMediumJD
Controller remap UIBacklogLowKM
Launch trailer cut 3BlockedCriticalJD

02Documents

Pages that link to
live records.

Write the decision in a page and mention the records it affects. Rename the record later and the mention updates.

  • Comments, suggested edits and full history on every page
  • Embed a view inside a page and it stays editable
Workspace/Design pillars

Design pillars

Share
ARAR is editing · saved 2m ago
Pillar 2 — Readability

Exception: vertical slice builds may ship unlit.

03Canvas

A canvas where the
nodes are records.

Map a process on an infinite board. Each node opens the record it points at, and a board dropped on the canvas keeps working.

  • Wires between nodes can carry data
  • Draw the flow, then turn it into an automation
Workspace/Level flow

Level flow

100% Draw
what breaks first?
Greybox3 tasks
playtest here
Ship gateGated

04Dashboards

Dashboards that read
the live data.

Counts, trends and lists computed from the records people are editing now. Nobody exports a spreadsheet to make one.

  • Widgets are queries, with the same permissions as views
  • One dashboard per team over the same database
Workspace/Today

Today

This weekEdit
6
Due today · +2
1
Blocked · −1
12
Shipped · +5
Tasks closed8 weeks
At risk2
Player controller feel passAR
Launch trailer cut 3JD

05Home

Home is about
your day.

Your assignments, your mentions and what moved overnight, gathered from every surface you have access to.

  • Built from your permissions, so it needs no setup
  • Pin the views you open first
Workspace/Home

Still up, Ada 🌙

New
Anything in this workspace — ask, create, automate.⌘J
5Assigned
2Mentions
8Moved overnight
Assigned to you4
Player controller feel passDesign9:00AR
Boss arena blockoutArt11:30KM
Save system migrationEngineering14:00TL
Steam page copyMarketing16:15JD

06Automations

Automations written
as sentences.

When a field changes, do something. Every run keeps a log you can open, and every run can be undone.

  • Trigger on any field on any surface
  • Loop over every record in a database
Workspace/Notify on blocked

Notify on blocked

EnabledRun
WhenStatus becomesBlocked
AndPriority isCritical
ThenPingthe producer
Recent runslast 24h
Launch trailer cut 314:02
Save system migration09:41
Audio middleware spike08:15

Same blocks, different city.

Pick a kind of team and watch the layout change.

Art and Engineering carry the weight; Publishing stays a shed until launch month. Every district reads the same production database, so a slipped blockout moves the trailer date without anyone re-keying it.

DesignPillars, systems, feelProductionThe board it all hangs offArtBlockout to finalEngineeringBuilds and bugsAudioMiddleware, mixesQAPlaytests, repros

And the rest of it.

Everyday parts that do not need a demo.

  • Permissions per view

    Share a filtered view without sharing the database behind it.

  • Full history

    Every record keeps every version. Undo goes back as far as you need.

  • Real-time

    Two people edit the same record and both see it change.

  • Works offline

    Keep editing without a connection. Changes merge when you are back.

  • Relations and rollups

    Link records across databases and read through the link.

  • Formulas

    Computed fields that update when the fields they read change.

  • Forms

    A public form that writes into a database.

  • Comments

    On any record, block or cell. Threads stay attached to the thing.

  • Import

    Notion, ClickUp, Jira and CSV.

  • MCP server

    Connect your own agents. They get exactly your permissions.

  • Mobile

    iOS and Android apps. Desktop for macOS and Windows is in progress.

  • Export

    Any database exports to CSV. Files download as they are.

FAQs

Questions, answered

What people ask before they sign up.

A workspace where a team keeps its pages, databases, boards, dashboards, canvases and automations together, all reading the same records. You can change the structure later without exporting anything.

Snoze works without the assistant turned on. When you use it, it builds with the same databases, views and pages you would, and marks what it made in violet so you can see what changed.

Shape work. Then reshape it.

Free to start. No card. Describe your first workspace and it is ready in a minute.

Start freeTalk to us