How new projects come about
A link archive has turned into 13 projects. Almost every one came from a real need – not from a plan.
If you look at the projects page, you now see 13 projects. It looks as if someone had a big plan. The truth is simpler: almost every project came from a problem I had myself at that moment.
The pattern: one need, one building block, one project
| Project | Where it came from |
|---|---|
| RelyperAV | Saved pages had to be checked for malware. The scanner was built for Relyper itself – today it is a project of its own. |
| Relyper Links | One topic often has many sources. The smart links (first commits in February 2026) became link.relyper.de. |
| Relyper Neural Net | A live animated view of everything the platform is processing: every running job becomes a glowing node – the heartbeat of the system. |
| Relyper Browser Extension | Saving should take a single click (August 2026). |
| Relyper AI Factory | The platform on which many of the other projects were built and run (first factory commits in June 2026). |
| Jarvis & Aivra | Personal AI agents in the AI Factory – with telephony since October 2026. |
| Relyper Music | Relyper is also my artist name. The songs carry the same attitude: no tracking, no clickbait. |
| Relyper Piano, Case, Identity … | Ideas of my own that build on the same building blocks. |
Why it works
No new project starts from zero. It uses what is already there: login, coins for billing, the virus scanner, the AI proxy with its keys, tenant management. Telephony, for example, bills through the same coins as Relyper Case and gets its AI keys through the same proxy.
Explained simply: Think of it like Lego. At the start you build the bricks – login, payments, security. After that every new model goes faster because the bricks already exist.
And the core?
The core stays the link system. It is what Relyper is built on and what most of the building blocks go back to. Why all of this is still not “too much” is the topic of the post Too much? Or the new age of AI?
