The most interesting work happens before it has a name.
Before the deck, before the spec, before the design review, there's a stage where you're still gathering, still arguing with yourself, still putting things next to each other to see what they say. Some of this work is solo. A lot of it is shared. Two or three people circle the same question, leaving each other artifacts: a screenshot, a link, a thought half-finished.
This work has no obvious home. It isn't a document, a design, or a meeting. Most teams handle it by stuffing it into whatever tool is closest: a Slack channel, a Figma file, a Miro board, a Google Doc with twelve embedded images and growing.
None of those tools were built for this. They tolerate it.
The workshop assumption
The dominant collaborative canvas tools were built for a specific scene. A facilitator. A remote workshop. A structured exercise. Sticky notes get clustered. Voting dots get distributed. Outcomes get exported. The whole grammar of templates, timers, sprint modes, and breakouts assumes the work has a beginning, a middle, and a deliverable.
Most thinking doesn't work that way.
Most thinking is a loop you've been in for two weeks and a tab you keep open and a feeling that something is almost right. The shape it wants is closer to a wall than a workshop. A surface where things can sit and be looked at and rearranged and waited on. A surface where nothing demands resolution.
Tools built around the workshop metaphor punish you for using them this way. They want you to converge. They put a clock on quiet work.
What restraint actually means
There's a marketing version of "minimal" that means we have a clean UI. That isn't what we mean.
The restraint we care about is structural. It concerns what the tool refuses to do, less as an aesthetic gesture and more because doing those things would change the shape of the work itself.
A canvas with no templates makes you start from nothing. That's the point. A canvas with no export flow keeps the work unfinished by design. A canvas without dashboards or sprint modes refuses to dress half-formed thinking up as a deliverable. A canvas where the artifact is a URL rather than a file treats early work as something living, something still in motion.
Each of these is a no. Together they form a posture: this is a place where things can stay rough.
The room, not the meeting
We sometimes describe what we're building as a shared scratchpad, which is fine but undersells it. The better picture is older. A studio wall. A reference desk. A corkboard above someone's monitor that the whole team can see. Things go up. Things move around. Sometimes a thing stays up for months and then comes down without comment.
The work that happens around such a wall is the residue of attention. People notice what's there, add to it, take from it, walk past it. The wall does its job by being available.
A lot of remote-first software has spent the last decade trying to recreate the meeting. We're more interested in recreating the room.
Less, on purpose
The premise is straightforward. If you make the surface quiet enough, the right kind of work will move there on its own. The moodboard before the pitch. The screenshots you're still figuring out what to do with. The research wall three people keep adding to. The rough shape of an argument, pinned up before the deck.
These were never meant to be documents. They shouldn't have to become them.
What we're trying to build is the smallest possible thing that holds this work without distorting it. Something closer to paper than software. Something closer to a wall than a workspace.
It's called Oppalin. The room is yours.