01
Ownership
We build products of our own. We treat every client project with the same logic: as if we’ll be the ones operating it for the next ten years.
Team
Kronn was founded by Konstantinos Maris — a software and sales engineer with years of experience building software and making it sell. That combination defines how we work: every technical decision is judged by whether it produces business results.
Around him, a team of new-generation software engineers — each with years of experience in their field: development, infrastructure, design, marketing. We are small enough that you always talk to the people writing the code, and experienced enough that we don’t learn on your projects.
Our name is our contract: from χρόνος (time) and cron — the Linux process that executes exactly when it should, quietly, every time. That is how we want to be remembered: as the team that delivers on time.
01
We build products of our own. We treat every client project with the same logic: as if we’ll be the ones operating it for the next ten years.
02
Clear proposals, realistic timelines, bad news early. If something isn’t worth paying for, we’ll be the first to tell you.
03
We deliver when we said we would. Like a cron job: scheduled, dependable, no surprises.
You don’t have to take our word for it — these hold on every project we deliver, regardless of size:
[deploy] ok
Every change reaches production through an automated pipeline — not files copied to a server by hand.
[vcs] ok
Code, configuration and infrastructure with full change history and the ability to roll back to any previous version.
[backup] ok
Automated database backups — and a restore procedure that has actually been tested, not merely promised.
[monitor] ok
Systems are watched around the clock. When something drifts, we find out — before your customers notice.
[security] ok
Secure API design, minimal data collection and GDPR compliance by design — not bolted on afterwards.
[handover] ok
The code, the access and the documentation belong to you. We keep clients by earning it — not by locking you in.
Next run: now
Tell us what you want to achieve. You will get a clear, technically grounded proposal back — no fluff, no obligation.