About
We build things worth building.
Red Dot Industries builds B2B and B2C software. We design, build, and operate our own products from the ground up — no client work, no consulting.
We are a small team. We set our own standards, move at our own pace, and ship when things are right.
Our current portfolio is Obtura and Scalple. Both solve real technical problems. Both are built to production standards. Neither will be sold or shut down for a trend cycle.
Leadership
Alexandru Serban Nicolae
Founder & CEO
Software developer turned founder. Started in game development, progressed through systems programming in C++ and Assembly, and now builds full-stack products at the intersection of developer tooling and infrastructure security.
Founded Red Dot Industries to build software worth building — products with genuine technical depth, engineered to last. Scalple and Obtura are the first two.
How we work
Operating principles.
These are not aspirational values. They are the constraints we impose on every decision.
Precision over velocity
We ship when it's right, not when it's fast. Velocity is a means, not a goal.
Documentation is the product
If it isn't written down, it doesn't exist. Every system, every decision, every API.
No black boxes
Every system we build can be fully audited and understood. We don't build magic.
Correctness is not optional
Types, tests, and specifications are non-negotiable. Not best practices. Requirements.
Users are engineers
We design for intelligence, not the lowest common denominator. Our users can read a stack trace.
Operate from first principles
We don't follow trend cycles. We ask why until we reach a bedrock answer.
Team
A focused team.
We are a small founding team. We hire carefully and stay small on purpose — more people does not mean better software.
Roles
- Principal Engineer
- Systems Architect
- Product Lead
- Infrastructure Engineer
Process
Spec before code.
Every product begins with a written specification. We define the problem, the constraints, and the acceptance criteria before writing a single line of implementation code.
Architecture decisions are recorded as ADRs. Engineering conventions are documented and enforced via tooling. Nothing lives only in someone's head.
Read the process