I’m experimenting with software that grows slowly and explains itself over time

I’ve been working on a project called Space.

It’s not a typical SaaS and it’s not trying to be efficient in the usual ways. There’s no onboarding funnel, no dashboard-first experience, and no pressure to define everything upfront. Instead, it’s a living environment of systems that evolve publicly on a fixed cadence (the 1st and 15th).

The core idea is simple:
What if software felt discovered instead of sold?

Rather than presenting users with a feature list, Space treats systems as destinations. Some are practical. Some are experimental. Some exist mainly to be understood. Each one explains itself gradually, through use and context, rather than documentation walls.

I built this because I kept running into the same pattern in my own projects: optimize too early, explain too much upfront, and you end up building for conversion instead of curiosity. I wanted to see what happens if you reverse that — slow the system down, let it breathe, and allow meaning to compound.

Space is live, free to explore, and intentionally small right now. There’s no growth push and no monetization pressure. Some users choose to support it simply because they want it to keep existing, which I find more interesting than forcing value extraction early.

I don’t know yet if “slow, observable software” is viable long-term — that’s part of the experiment. But so far, it’s been refreshing to build something that isn’t racing toward a pitch deck or a pricing page.

Happy to hear thoughts, especially from anyone who’s tried building outside the usual SaaS playbook.