40%+
Faster CI pipelines
Reduced Jenkins execution time while making builds reproducible.
Independent consulting · B2B SaaS
Complex systems.
A clearer baseline.
Founder-led infrastructure consulting for established software teams. Senior engineering judgment, hands-on work, and systems your team can own.
Independent expertise. Clear scope. Built to hand over.
Selected founder experience
From real production environments.3h 30m
Shorter release workflows
Automated a release process from three hours to thirty minutes.
150+
Developers on a critical platform
Led a Sentry migration across five major versions without downtime or data loss.
Results from Nikita’s prior in-house engineering roles. Not Operational Baseline client engagements or guarantees of future results.
01 / Areas of expertise
The systems behind
the software.
Practical depth across software delivery and operations. I start with the systems your team already runs and the problems you’re facing.
01
Release engineering
CI/CD workflows, reproducible builds, artifact delivery, and deployment processes that teams can understand and maintain.
Jenkins · GitLab CI · GitHub Actions
02
Reliability & observability
Useful monitoring, actionable alerting, and engineering follow-through on the operational issues that keep coming back.
Metrics · Logs · Alerts · Recovery
03
Infrastructure & migrations
Self-hosted platforms, infrastructure automation, secrets management, and carefully planned changes to critical systems.
Linux · IaC · Containers · Vault
02 / The person behind the work
Nikita Tsepov
Founder & Principal Consultant
Based in the APAC regionWorking internationally
View LinkedIn
Senior expertise.
Direct accountability.
I’m Nikita, a DevOps and SRE engineer with 6+ years of experience in high-transaction, security-sensitive software environments.
My background spans release automation, multi-region infrastructure, observability, and difficult migrations. Operational Baseline brings that hands-on experience to established B2B SaaS teams.
I work directly with engineering leaders and the people who will maintain the system afterward. Clear decisions, documented changes, and knowledge transfer are part of the work.
03 / Current research
Listening before
prescribing.
I’m speaking with CTOs, VPs of Engineering, and platform leaders about the infrastructure problems that matter most — and when outside expertise is actually useful.
Have a perspective
worth sharing?
These conversations inform service development. Nothing is attributed to you or your company without your permission.
04 / Contact
Start with
a conversation.
A research perspective, an introduction, or an engineering question. A short email is enough.
nikita@No forms to fill in. Just a direct conversation.