Principles for building simply.
We don't chase trends.
We choose structures that don't change with time.
Principles
Focus on what doesn't change
Tools change. AI keeps producing faster ones.
But the infrastructure of web spaces, messaging and email has stayed the same.
We attach new tools to the ones you already know.
Simplicity that doesn't need to chase trends.
Keep what you see light
A good tool needs no manual.
As features pile up and the screen gets busy, software gets harder to learn and use.
We build software that is easy to understand.
Put the effort where you can't see it
We spend the most time on work nobody will notice.
Security design, performance tuning, data structures that can grow.
And so that what we build is fully yours,
we think about technical rights and legal protection too.
Data sovereignty
It belongs to the people who create it.
On your server, on your disk.
Local-first. Simple to use, fully owned.
The people building it
Sun
"I think about building it right before building it fast."
I have designed and built software for 26 years.
From enterprise systems integration to founding startups, I have seen why software fails and why it survives.
Writing good code is the baseline.
I first ask why it has to be this structure, and whether the design will still be right in three years.
I don't pick technology by what is in fashion.
I pick the most sensible structure for the customer's environment.
Hey
"I look at why we are building it first."
I started as a patent attorney, became a startup CEO, and am now in my fifth year as a developer.
I founded a healthcare data startup, failed, and am building again.
Technology alone doesn't make a product.
I first look at whose problem we are solving, and whether solving it can make money.
So that what we build is fully the customer's,
I design the technical rights and legal protection alongside it.
A hard problem?
We'll work through it with you.
A vague worry is fine too. Get in touch any time.