Digital Sovereignty as a Designer

For a long time, the digital landscape felt like a "walled garden" fever dream. My creative life was scattered across proprietary ecosystems - Google Workspace, Figma, and Apple—where I was a tenant, not an owner. This year, I decided to wake up and plant my own garden.

I migrated my entire digital existence to a self-hosted Nextcloud instance. The shift wasn't just about moving files; it was about regaining ownership, knowledge, independence, and focus.

The Designer’s Migration: From Tenant to Architect

As designers, we often ignore the "Friction Tax" of proprietary tools because they are polished. But when our data is fragmented across services, we lose the ability to act independently.

My journey this year has been about consistent transitions. Inspired by Digital Independence Day, I’ve adopted a simple rule: on the first Sunday of every month, I transition one service or tool to a sovereign one.

So far, my stack has evolved significantly:

CategoryProprietary (Before)Sovereign (Now)
OSiOSAndroid (better would be GrapheneOS or actual Linux)
PhotosGoogle & Apple PhotosNextcloud Photos with AutoSync on Android
StorageGoogle Drive, OneDrive, iCloudNextcloud
OfficeMS Office / Google WorkspaceNextcloud Office
PodcastsApple Podcasts / SpotifyAntennaPod
MusicApple Music / SpotifyNextcloud Music
PasswordsApple PasswordsKeepass hosted on Nextcloud
  • Nextcloud now serves as my unified hub for files, contacts, and cards.
  • Moving away from scattered services eliminated the mental "switch cost," allowing for deeper focus, more intentional use of my technologies.
  • By using open-source alternatives like Penpot, I’ve secured my workflow against vendor lock-in and unpredictable price hikes.

Why Designers Should Contribute to Open Source

Digital sovereignty is not just a technical requirement; it is a design principle. Many open-source projects (OSS) are powerful but lack "grandma-level usability" because they are built by developers for developers. Many tools in the open source world originated from someone who tried to fix a technical problem, not make it pretty for end users right away. This is a massive opportunity for our community.

  • The Grandma Test: Visit your family and try to set these tools up together. If a tool doesn’t pass the "Grandma Test," don't just walk away. Help the open source community improve it.
  • Humanizing Infrastructure: We can bridge the gap between complex code and intuitive user experiences. Submit an issue on GitHub, send feedback to the developers, or offer a UI mockup. By doing so, we make sovereign tools accessible to everyone, not just the tech-literate.
  • Long-term Skill Growth: Contributing to OSS allows us to shape the very tools we use, refining them to meet professional industry requirements rather than just following a vendor's roadmap.
  • Democratic Design: Open-source platforms like Decidim enable publicly governed digital spaces. Designers can help build these "digital commons" for democratic discourse.

AI: The Tutor for Independence

The "fear" of self-hosting—managing servers and fixing broken configs—is being dismantled by AI.

  • AI Assistants: I now use AI as a technical curator to navigate complex setups. It helps bridge the literacy gap by explaining terminal commands or debugging local-first software.
  • No-Code Sovereignty: Tools like NocoBase or ToolJet allow designers to build internal tools visually while maintaining full data ownership on their own servers.

Low-Bar Entry: Try Managed, Then Own

I grew up as a "Linux kid" and deployed web projects - the console and admin tasks are pretty familiar to me and LLMs combined with available documentation have become a great guidance for complex tasks.

You don’t have to be a SysAdmin to start. Nextcloud makes it easy to try a managed hosting variant where a provider handles updates and backups. This is the perfect "test drive" for designers.

  • Step 1: Start with managed hosting to get the feel of the ecosystem.
  • Step 2: Once you’re familiar, migrate your setup to your own hardware. I personally use a Raspberry Pi at home to run my cloud as a Docker image. This setup gives me the flexibility to host all sorts of other services—like Penpot or local automation tools—alongside Nextcloud.

If managing hardware isn't your thing, it's totally possible to host your instance on providers like IONOS or Hetzner. You can check the Nextcloud website for partnering hosters that offer simple one-click setups.

My Sunday Plan: I’m replacing one more proprietary service today. What about you? Start small. Reclaim your tools. Plant your garden.

Resources to Start Your Migration: