Welcome

We blend strategy, design and engineering to build intelligent systems that help businesses in Saudi Arabia and the GCC grow and stand out.

How we pick a database

Why Postgres is the default — and usually the final answer.

Engineering10 min read

Many teams spend weeks comparing databases, then regret the choice a year later. We have a simple rule: start with Postgres, and don't leave it except for a reason you can name.

The boring default

Postgres is mature, reliable, and does more than most people think: text, JSON, search, even vectors. Most products will never outgrow it, and boring here is a feature, not a flaw.

When to leave

There are real reasons to move: a massive analytical load, large time-series data, or geo-distribution requirements. But they're reasons measured in numbers, not fashion.

The hidden cost of variety

Every additional database means new expertise, new backups, and a new point of failure. Standardising on one you know well beats owning four you half-understand.

Choose boring, measure constantly, and leave when the numbers force you — not before.

Newer article

Say no to features

Read more

Read more

All articles
Engineering

How we architect for scale

8 min read

Thinking

Say no to features

4 min read

AI

Arabic RAG — what we're learning

7 min read

Contact us