[{"data":1,"prerenderedAt":19},["ShallowReactive",2],{"blog:workspace-vendor-or-operator":3},{"title":4,"description":5,"date":6,"author":7,"url":8,"markdownPath":9,"html":10,"toc":11},"Your workspace stack has a landlord problem","Slack, Notion and hosted tools make work convenient. They also make their operators' decisions part of your operating model.","2026-10-30","Inchi","\u002Fblog\u002Fworkspace-vendor-or-operator","\u002Fblog\u002Fworkspace-vendor-or-operator.md","\u003Cp>Your team chat is in Slack. Your documents are in Notion. Your task tracker is somewhere else. Each product is convenient on its own. Together, they mean your work depends on several vendors, several accounts, several permission models and whatever each provider decides to change next.\u003C\u002Fp>\n\u003Cp>This is not a conspiracy. Hosted services cost money to run, and vendors set terms for their products. \u003Ca href=\"https:\u002F\u002Fslack.com\u002Fhelp\u002Farticles\u002F115002422943-Usage-limits-for-free-workspaces\" rel=\"noopener\">Slack's free plan shows the last 90 days of messages and files\u003C\u002Fa>; \u003Ca href=\"https:\u002F\u002Fwww.notion.com\u002Fen-gb\u002Fhelp\u002Fexport-your-content\" rel=\"noopener\">Notion provides exports\u003C\u002Fa> but its database export does not include every view at once. Those are concrete product choices. The larger problem is treating those choices as if they were invisible infrastructure.\u003C\u002Fp>\n\u003Ch2 id=\"a-different-default\">\u003Ca class=\"heading-anchor\" href=\"#a-different-default\">A different default\u003C\u002Fa>\u003C\u002Fh2>\n\u003Cp>L4 is MIT-licensed software for running an independent Server. The Server keeps its Accounts, permissions and content local to that community. The Shell is a convenient way to navigate between Servers, not a global membership authority. Operators run it on their own Cloudflare account or self-host it on a VPS, and keep backups separate from live data.\u003C\u002Fp>\n\u003Cp>That changes who has work to do. Your operator needs infrastructure, a secure setup, updates and a recovery plan. Providers can still change their prices or suffer outages. Open source does not abolish dependencies; it gives you more control over which ones you accept and how you respond.\u003C\u002Fp>\n\u003Ch2 id=\"dont-move-on-slogans\">\u003Ca class=\"heading-anchor\" href=\"#dont-move-on-slogans\">Don't move on slogans\u003C\u002Fa>\u003C\u002Fh2>\n\u003Cp>The mature products in your stack may offer capabilities L4 does not. There is no promise of an automatic import from Slack or Notion, full feature parity, or zero-cost hosting. Before moving real work, list the workflows you actually use, test permissions with two people, verify files and recovery, and keep your existing data until you have a plan.\u003C\u002Fp>\n\u003Cp>We are building toward a workspace that is easier to operate without giving up the community's authority over it. Judge that claim by the install, the everyday workflow and the restore—not by the size of the “open source” label.\u003C\u002Fp>\n\u003Cp>\u003Cem>Slack and Notion details checked October 29, 2026 (\u003Ca href=\"https:\u002F\u002Fslack.com\u002Fhelp\u002Farticles\u002F115002422943-Usage-limits-for-free-workspaces\" rel=\"noopener\">Slack: Usage limits for free workspaces\u003C\u002Fa>, \u003Ca href=\"https:\u002F\u002Fwww.notion.com\u002Fen-gb\u002Fhelp\u002Fexport-your-content\" rel=\"noopener\">Notion: Export your content\u003C\u002Fa>).\u003C\u002Fem>\u003C\u002Fp>\n",[12,16],{"id":13,"text":14,"depth":15},"a-different-default","A different default",2,{"id":17,"text":18,"depth":15},"dont-move-on-slogans","Don&39;t move on slogans",1793335826521]