Team
One entrepreneur, one team
Janzin Holding is run by Danijel Janzin. Day-to-day operations are handled by a team of 34 agents – each with a fixed job, from locking away access credentials to checking that a site really answers after an update. Decisions are made by a human.
How we work
The team by area*
Owner1

Danijel Janzin
Founder and owner
Entrepreneur in Munich since 2009. Founds the brands, decides their direction and is responsible for everything under the Janzin Holding roof.
Leadership1

Lena
Chief of Staff
Keeps the six heads of department together and brings decisions to Danijel Janzin before they escalate.
What is decided today does not escalate tomorrow.
Security & compliance7

Omar
Head of Security & Compliance
Responsible for access credentials, identities and hardening across the whole environment.
Trust is good, evidence is better.

Erik
Credential custody
Creates access credentials and locks them away before anyone gets to see them.
A value nobody reads is a value nobody can lose.

Jack
Pre-flight review
Reads every plan before a secret leaves the room.
A false alarm costs minutes, a leak costs money.

Sarah
Application security
Finds the hole in the plugin before it goes live.
A negative finding needs the same evidence as a positive one.

Maria
Vault upkeep
Keeps the password vault cleanly tagged and free of duplicates.
Order is a security measure.

Barbara
Identity & access
Checks every login integration and knows which redirect address belongs to it.
Whoever should get in gets in. Nobody else does.

Sebastian
Infrastructure hardening
Checks every machine for firewall, SSH access and updates, fresh every time.
Last verified is no reason not to look.
Infrastructure & operations8

Ingrid
Head of Infrastructure & Operations
Responsible for databases, networks, backups and platforms, so everything runs before anyone has to ask.
What is not backed up is only ours for a while.

Simon
Database operations
Gives database users exactly the rights they need, and no more.
Least privilege is not an opinion.

Marco
Network operations
Keeps DNS records correct across all domains.
A record only counts once it has been checked.

Andrea
Cloud operations
Rolls out cloud changes so the second run does the same as the first.
Idempotent means pressing it again is allowed.

Robert
Operational safety
Runs deploys, backups and updates on the app server.
Look first, then act.

Melanie
Backup & recovery
Shows what is backed up and what is missing.
A backup that was never restored is an assumption.

Leonardo
Platform operations
Knows every trap in the document management stack.
Diagnosis before fix.

Anderson
Platform operations, analytics
Checks that the analytics platform runs healthy: cron, backup, tracker.
Tracking can run while the interface hangs. So check both.
Support & delivery7

Marina
Head of Support & Delivery
Makes sure mail arrives, alerts are right and the helpdesk answers.
Whoever listens needs fewer escalations.

Nora
Hosting operations
Checks after every change whether the site really answers.
A site is only done once it answers.

Julian
Email operations
Connects a website's mail sending to the right delivery service.
The sender has to match the domain.

Nadia
Deliverability
Tracks whether outgoing mail arrives: DKIM, SPF, DMARC, bounces.
Sent is not delivered.

Hannah
Customer service operations
Keeps the helpdesk running from incoming mail to reply.
Behind every ticket is someone waiting.

Anthony
Coverage
Checks that every scheduled job has a monitor and every monitor a job.
A check without a job is a dead alarm.

Vanessa
Alert quality
Spots alerts that only fire at the wrong time of day.
It was never the job, it was the clock.
QA & reliability6

Rebecca
Head of QA & Reliability
Sets the bar: nothing counts as done until it is proven.
A passing test proves nothing as long as it has never failed.

Thomas
Data integrity
Confirms that nothing gets lost when archiving.
After archiving nothing is missing, not even a single line.

Michael
Release verification
Proves that a service actually serves, rather than just running.
Running does not mean serving.

Frederik
Script reliability
Finds scripts that fail silently.
Silent failures are the most expensive.

Isabella
Release verification, dashboard
Approves changes to the usage dashboard only when data and display match.
Numbers first, then the picture.

Gabrielle
Frontend review
Checks frontend changes against the project's house style.
New things adapt to the house style, not the other way round.
IT support3

Sofia
Head of IT Support
Keeps the work devices healthy and the team calm.
A service nobody notices is a good service.

Emma
Device health
Finds what drains battery and spins up fans.
No claim without evidence.

Neil
Device care
Clears out leftovers of uninstalled apps, never without the trash.
Clean up, but never without a way back.
Documentation2

Pavel
Head of Documentation
Responsible for the company's knowledge: findable, sourced and up to date.
Knowledge nobody can find is no knowledge.

Alexandra
Knowledge management
Runs the wiki check: dead links, stale pages, missing details.
A link that points nowhere is an open item.
Contact
Questions for the team?
A human will answer. Write to us – usually within two business days.
* Apart from Danijel Janzin, names and portraits are AI-generated and do not show real people. The jobs behind them are real: this is how our brands are run every day.
