Why SandsteinLabs?

Software projects rarely begin in the same place. Sometimes there is a concrete problem. Sometimes an existing solution feels more complicated than it needs to be. And sometimes there is simply an idea where the most interesting question is: what happens if you actually build it?

That is what SandsteinLabs is for.

The name deliberately does not promise one narrow category. SandsteinLabs is not a product type and it does not prescribe whether something has to become a mobile app, a web tool, or a technical experiment. The common denominator is less about format and more about care: an idea should get the chance to be thought through properly and developed far enough that an experiment can become an actual product.

Why a separate name?

Building software outside of work has been normal for me for a long time. It started with simple HTML and CSS pages. Later came frontend frameworks, backends, more complex web applications, and eventually native and mobile apps.

At some point, I wanted those projects to be more than a loose collection. A shared name creates a frame without forcing every product to look the same. That is exactly what SandsteinLabs should be: a stable parent brand under which products are free to have their own identity.

Why sandstone?

Dresden is part of this project. Not as a marketing motif, but as its origin.

The Elbe Sandstone Mountains are close by, with a landscape whose forms are instantly recognisable. The rocks, the Bastei, and the layered depth of the scenery feel organic and surprisingly clear at the same time. That combination fits what SandsteinLabs should be visually: warm and regionally rooted, but precise and modern in execution.

That is why the landscape does not appear as a large photograph on every page. It lives more abstractly in the name, the mark, and a small number of visual forms across the site.

A lab, not a backlog

The "Labs" in the name does not mean every experiment has to be documented publicly. Quite the opposite. SandsteinLabs is not meant to be an open Kanban board.

Ideas may remain unfinished, be discarded, or exist only to teach something. The public project collection only contains work that has reached a point where it can stand as a real product. Version 1.0 is therefore less a technical number than an editorial decision: this project is ready to be shown and handed to other people.

Where that leads

That is deliberately open.

Maybe SandsteinLabs will produce small useful apps. Maybe one idea will grow into a larger product. Maybe some things will remain experiments. The important part is not deciding the size of the outcome in advance, but taking the quality of the execution seriously.

SandsteinLabs is, above all, a place where software ideas get a frame — and where there is room to find out what they can become.