Flocci Workspaces: One Canvas to Close the Twelve Tabs

Count the tabs. Go on — count the ones open right now, the ones you keep open not because you’re using them but because closing them means the friction of finding them again. Trello for the board. Notion for the doc. Google Calendar for the week. A notes app for the thing you’ll forget. Todoist for the list, a video tab for the call at three, a spreadsheet standing in for a database you never built. Twelve tabs to do one job, and the job is just keeping track of your own work. Every switch is a half-second of reorientation — find the tab, remember where you were, pick the thread back up — and across a dozen tabs those half-seconds pile into the cost nobody ever puts on the bill: the compounding price of context-switching between a stack of tools that were each supposed to save you time.

The tab is a confession

Here’s what the row of tabs actually admits: no single tool trusts itself to hold your whole workflow, so each one takes a slice and hands the seams back to you. Trello knows about cards but nothing about your Tuesday. Your calendar knows about Tuesday but nothing about the card. The document that explains why the card exists lives in a third app that has never heard of either. You are the integration layer. You are the human API stitching ten disconnected products together with copy-paste and memory, and the stitching is invisible labor that no productivity guru counts.

The all-in-one dashboards that promised to fix this mostly didn’t. They gave you kanban and sticky notes and called it a workflow — a corkboard, not a workspace. The moment you needed a real document with structure, or a table you could actually query, or a video call without leaving the page, you were back in the tabs. The category’s dirty secret is that “all-in-one” usually means “the two or three tools that were easy to build, bolted together.” The hard primitives — block documents, typed databases, live video — got left out, and left out is exactly where the tabs come from.

One canvas, eight real tools

The substrate is a 12-column grid — react-grid-layout under the hood — and the grid is the point, not decoration. Panels drag, resize, and snap in true column units, and the layout persists per workspace, so the arrangement you build is the arrangement you return to. Older quadrant layouts auto-migrate into the new grid units rather than breaking. But a grid is only as good as what you can put in it, and this is where Workspaces separates itself from the corkboards: the panels aren’t widgets, they’re genuine tools.

That Pages-and-Databases pairing is the tell. Most “productivity dashboards” stop at kanban and sticky notes because block documents and typed databases are genuinely hard to build — and they’re exactly the two things you leave to open Notion for. Workspaces ships both as first-class canvas panels. The database isn’t a table pasted into a note; it’s a real record set you can view four ways and query with filters and group-by, the piece that turns a wall of freeform notes into data you can actually ask questions of. Round it out with a day/week/month calendar, sticky notes and checklists on an infinite canvas, a floating pomodoro timer with work and break sessions, and a timetable planner with categories and completion tracking, and the twelve tabs collapse into one screen you never leave.

Two products wearing one codebase

Here’s the split personality, and it’s a feature, not a compromise. The public site sells Workspaces as an individual, free, no-signup, local-first tool: “100% private — all data stored locally,” core tools that run on local-storage adapters with no account at all. That’s real. It’s also only half the product. Sign in through Flocci’s shared identity and the same canvas becomes a live, multi-user team platform — shared workspaces, presence, and a real-time layer that broadcasts updates across kanban, notes, pages, and databases so a teammate’s edit lands on your screen without a refresh.

What’s quietly excellent is that Workspaces is honest about which mode you’re in. It self-probes a public /health/capabilities endpoint every thirty seconds and tells you the truth: online, degraded, or offline. When real-time isn’t available you get a plain banner — “Serverless mode — real-time collaboration is unavailable; all other features work normally” — instead of a spinner that lies or a sync that silently drops your work. Three states, named out loud. In a category built on optimistic UIs that pretend nothing ever fails, that candor is its own kind of luxury.

How the collaboration actually holds together

1. You sign in once, everywhere

   Auth is fully delegated to Flocci’s shared identity service — Google SSO through the platform gateway. The old local password model was deleted outright; every request and every socket verifies RS256 tokens through JWKS, so one Flocci account works across the whole estate.

2. Presence and membership get verified on join

   The Socket.io /workspace namespace checks your token against the identity service and re-confirms your workspace membership when you join — presence and live updates only flow to people who actually belong in the room.

3. Edits broadcast as they happen

   Move a card, type in a page, patch a database cell — the change fans out to every connected client in the workspace. A five-tier role model (Owner/Admin/Editor/Viewer/Member) governs who can do what, enforced by per-module access checks.

4. Share out without minting accounts

   Any page can be published to a read-only public URL — its own clean TipTap render — with an optional scrypt-hashed password, an expiry date (a 410 when it lapses), and a view counter. Recipients read; they never need to log in.

The engineering underneath is not toy-shaped. A NestJS backend with roughly 110 REST endpoints across 19 controllers, a 30-model Prisma schema over PostgreSQL, Socket.io for realtime, Swagger docs at /api/docs. The kanban module alone spans 25 endpoints; databases ship 15. This is a platform pretending, on its homepage, to be a cute personal dashboard — and mostly the homepage just hasn’t caught up. Pages, Databases, Meetings, Share Links, and the cross-app agenda are all live in the build but not yet reflected in the marketing copy, which means the product currently undersells itself. That’s a rare direction for software to err in.

Not an island

Workspaces doesn’t hoard your context — it federates it. The standout is My Day: a unified agenda that merges the workspace’s own kanban and calendar with projects, notes, and events pulled from Flocci Work Apps, server-to-server, honoring your active org. A background realtime bridge re-emits Work Apps changes into your personal room, so your cross-app agenda stays live instead of going stale the moment you tab away. And every meaningful action — a collection created, a meeting started — is emitted onto Flocci’s Graph event mesh through a live outbox drained into Redis Streams, carrying a proper app/user/idempotency/privacy envelope. Workspaces is a full-tier citizen of the platform, inheriting identity, notifications, and the event graph instead of rebuilding them.

The analyst that’s still asleep

And then there’s the part that we keep coming back to. Flocci Workspaces is carrying a fully-built brain it has never switched on. Roughly 90KB of finished intelligence code — a burnout-risk scorer, a task-completion predictor, a forecast generator, an anomaly detector, and an A+-to-F team-health grader — sits inside the codebase completely dormant, deliberately kept out of every module’s providers array so dependency injection never instantiates it and its scheduled snapshot jobs can never even fire. It isn’t a stub or a TODO. It’s written, and it’s unplugged, on purpose.

The irony is almost too neat. The productivity app whose entire promise is ending your overwhelm already knows how to detect your overwhelm — it can score burnout risk and grade a team’s health today, on paper — and it’s holding that capability in reserve behind a single deliberate decision. AI is the one shared Flocci service Workspaces hasn’t wired yet, and this dormant layer is precisely the intended activation point for the platform’s DeepSeek-backed intelligence. That’s not a gap; it’s a loaded spring. Most products ship the marketing and hope the engine follows. Workspaces built the engine first and left it idling, waiting for the moment someone decides it’s time to wake the analyst up.

Until then, what you get is already the honest thing the category has been promising for a decade and never delivered: one canvas, real primitives, live collaboration when you want it and dead-simple privacy when you don’t, and enough architectural seriousness underneath that the twelve tabs finally have somewhere to go. Close them. This is where the work lives now.