About
IDEAS NEED SPACE TO GROW.
NEO LABS is an independent software lab for digital products, tools and experiments.
Behind the Lab
Build. Understand. Improve.
NEO LABS is my space for software, ideas and technical experiments. It grew from a simple motivation: building things myself, understanding how systems really work and finding better solutions to everyday problems.
Some projects become complete products. Others deliberately remain experiments. Both matter.
It is about creating things that are thoughtful, understandable and genuinely useful.
Built by Neo.
The Name
A name that stayed.
Neo has been part of my digital identity for a long time.
What originally started as a nickname eventually became something that felt natural for the way I work and build software.
NEO LABS is not tied to one technology or one product.
It is the shared space for everything that can grow from it.
Products.Experiments.Tools.Ideas.
How I build
Software development is changing.
Modern development does not mean committing to one particular technology or tool.
It means finding the right solution for the problem.
I combine traditional software development with modern AI-assisted development workflows.
AI can help:
- explore ideas faster
- build prototypes
- challenge architecture
- analyse code
- compare alternatives
- reduce repetitive work
But the tool does not make the product decision.
Architecture, UX, privacy and technical quality remain deliberate decisions.
AI assisted. Human directed.
Technology
Modern technology. Sensible choices.
Technology should support the product, not become the product.
The stack can change. The principles should not.
Independence
Understanding systems means keeping control.
- Where is the data stored?
- Which services are required?
- Which dependencies are created?
- What happens if an external provider disappears?
Another part of NEO LABS is an interest in infrastructure.
Docker.Linux.Databases.APIs.Servers and self-hosted services.
Not because everything needs to be self-hosted.
But because understanding what happens behind an application matters.
Technical independence does not mean building everything yourself.
It means being able to make informed decisions.
Principles
- 01
Useful over impressive
A small solution that solves a real problem is more valuable than a large solution without purpose.
- 02
Simple over complicated
Complexity needs a reason.
- 03
Understand what you build
Tools may make development easier. The system behind them should still be understood.
- 04
Privacy by thought
Privacy is not a feature added at the end. It belongs in the architecture.
- 05
Build. Learn. Improve.
The first solution does not need to be perfect. But every iteration should improve something.
- 06
Stay curious
Curiosity is part of the development process.
Ideas into software.
Built with curiosity.
Current focus
- ProductBudgetplannerActive
- Experiment EXP-001AI Expense ClassificationExperimental
- Experiment EXP-002Receipt OCRPrototype
- Experiment EXP-003Self-hosted ServicesExploring
Contact
LET’S BUILD SOMETHING.
Have an idea, a question or simply want to say hi? I’m always interested in interesting problems, useful software and new possibilities.