i.FinOps wing
10–40%
Lower AWS costs after right-sizing, modernization and FinOps governance.
Boutique AWS Advanced Tier Services Partner · Tallinn
We build
and run AWS.
For companies that can't afford to get it wrong — Tidora is a boutique AWS Advanced Tier Services Partner and GitLab partner. One senior team for secure cloud platforms and modern software delivery, from first roadmap to the pager.
A boutique cloud team helping Baltic and CEE innovators migrate and scale with confidence.
NORDLINEVeritonKalda&CoPAGUShelix.Saarema
Output board · measured
Outcomes that matter.
Readings from recent engagements
Baltics · CEE · Nordics
ii.Cutover bay
< 1 min
Cutover downtime target for carefully planned cloud and GitLab migrations.
iii.Delivery line
20–50%
Faster software delivery with GitLab CI/CD, IaC, Kubernetes and platform engineering.
iv.Ops desk
24/7
Managed cloud operations available for production AWS and Kubernetes environments.
The line · five stations
Walk the hall.
Five stations, one senior team.
Each station maps to a wing of the plant
Tour proceeds in build order
01Station — Rack hall
AWS Cloud Infrastructure & Modernization
Secure, scalable, production-grade AWS environments — designed, built and modernized by senior engineers.
- AWS landing zones & multi-account architecture
- Kubernetes-EKS, networking, security & compliance
- Infrastructure as Code: Terraform & Crossplane
- Migration, modernization & performance optimization
02Station — Delivery line
GitLab, DevOps & Platform Engineering
Faster, safer software delivery on GitLab — resale, implementation, migration and developer-platform engineering.
- GitLab resale, implementation & migration
- GitLab CI/CD, DevSecOps pipelines & runner architecture
- Repository & pipeline migrations (GitHub, Jenkins, Bitbucket)
- Kubernetes deployment workflows & developer platforms
03Station — Data annex
AI & Data Solutions on AWS
Practical AI engineering on solid cloud foundations — built into real products, not slide decks.
- Amazon Bedrock, RAG systems & AI assistants
- Data pipelines, data architecture & personalization
- AI integration into SaaS products & workflows
- Secure environments & production deployment
04Station — Metering wing
AWS Resell & Cloud Cost Optimization
Better commercial terms backed by senior cloud engineering — not a discount-only relationship.
- AWS resale & consolidated billing
- Savings Plans & Reserved Instance guidance
- Cost reviews, FinOps & budget governance
- Architecture optimization & technical advisory included
05Station — Ops desk
Cloud Operations & Managed Services
Reliable day-to-day operation of AWS, Kubernetes and GitLab-based delivery environments — senior engineers on the pager.
- Managed AWS & managed Kubernetes-EKS
- Monitoring, incident response & on-call
- SLA-backed support & security operations
- Backup, recovery & patch management
- GitLab platform support & runner ops
- Continuous improvement & monthly reports
MSA · Clause, not copy
SLAs are written into the MSA, not the brochure.
Every engagement has a written success criterion agreed in week one. If we miss it for reasons within our control, we extend the engagement at our cost until it is met. This clause is in the contract, not a sales line.
Commissioning sequence
How we deliver.
A structured path from first roadmap to steady-state operations —
fixed phases, named owners, no surprises.
Phase 01Week 1–2
Discovery & Strategy
Two weeks. We read your architecture, your bill, and your incidents. You get a target architecture, ADRs, and a sequenced roadmap — defended in one readout.
PrincipalCloud Architect
Phase 02Week 3–8+
Foundation & Build
Landing zone, IaC, pipelines — built by the pod, demoed weekly, no clickops.
Tech Lead2–4 Senior Engineers
Phase 03Ongoing
Steady State
We take the pager, or we hand it over — 30-day shadow period, runbooks and dashboards included.
SRE LeadAccount Engineer
Tech scale-up cut migration downtime from days to minutes — unlocking 30% faster feature delivery.
Commissioning plaques
What we shipped, who shipped it,
and the number that moved.
Series B fintech180 engineersVilnius
Cut AWS spend 68% without slowing delivery.
−68% YoY
Re-platformed a sprawling EC2 estate to ECS Fargate with right-sized RDS, savings plans, and a strict tagging contract. Eight-week program, two cutover windows, zero customer-visible incidents.
Lead engineer — Karl TammResult — Spend ↓ 68% YoY
Mobility platform70 engineersTallinn
Off DigitalOcean and into AWS in 11 days.
11 days
One pod, one weekend cutover, full Terraform handover. They kept their CI green the whole time.
Lead — Liisa NõmmDuration — 11 days
European healthtech110 engineersRiga
From two outages a quarter to zero, in six months.
8 → 0 P1 / quarter
Introduced SLOs, blameless post-mortems, and a real on-call rotation. Migrated logs to CloudWatch + OpenSearch. The on-call engineer now sleeps through the night.
MTTR — 94 min → 19 minLead — Janis Ozols
Duty board · on rotation
The team.
Named engineers on every engagement
Tallinn · Riga · remote-first EU
Senior engineers design it, build it, and carry the pager for it.
No juniors on the roster ·No subcontracted on-call ·
Named owners in every SOW
Karl TammPrincipal Cloud ArchitectAWS SAP · DevOps Pro11 y
Liisa NõmmMigration LeadAWS SAA · Security8 y
Janis OzolsSRE LeadAWS DevOps Pro · CKA9 y
Mart SaarPrincipal EngineerAWS SAP · Database12 y
Eglė RagelisSenior Cloud EngineerAWS SAA · Security7 y
Andris BērziņšDevOps EngineerAWS DevOps Pro6 y
Work orders · four shapes
Engagement.
You will hear a ballpark on the first call,
not after three meetings.
DiscoveryW/O-01
Architecture assessment
A two-week sprint that ends with a defended target architecture and a sequenced roadmap.
2-week sprint · fixed scope
Book the assessment →Fixed-scopeW/O-02
Project SOW
One defined workstream — built, shipped and handed over. Fixed price, fixed deliverables, signed SOW.
4–10 weeks
Scope a project →Most picked
ProgramW/O-03
Migration program
A pod of senior engineers embeds with your team and delivers waved cutovers without freezing your roadmap.
8–20 weeks · waved cutovers
Scope a program →RetainerW/O-04
Managed AWS
We run AWS for you. Named engineers, 15-min P1 response, monthly reviews, full audit trail.
12-month minimum · 60-day exit
Talk retainer →Inspection log
Asked before signing.
Documentation, Terraform, runbooks, and dashboards stay with you — they were always yours.
Where does our data live, and are you EU/GDPR compliant?
Default deployment region is eu-central-1 (Frankfurt) or eu-north-1 (Stockholm). Tidora is GDPR-compliant, ISO 27001 in progress, and we sign DPAs and SCCs as standard. We never copy customer data out of the customer account.
What is the response SLA, and what counts as a P1?
Managed retainers carry a 15-minute P1 acknowledgement during EU business hours and 30 minutes on the 24/7 add-on. P1 = customer-impacting outage on a production workload we operate. SLAs are written into the MSA, not the brochure.
Do you offer 24/7 on-call?
Yes, as an add-on to the managed retainer. Rotation is staffed by named engineers from Tallinn and Riga, with PagerDuty integration into your existing alerting. We do not subcontract on-call.
What happens if the engagement underperforms?
Every engagement has a written success criterion agreed in week one. If we miss it for reasons within our control, we extend the engagement at our cost until it is met. This clause is in the contract, not a sales line.
Can you move us off GitHub, Jenkins, or Bitbucket?
Yes — repository and pipeline migrations are core GitLab practice work for us: CI/CD conversion, runner architecture, and developer-platform setup, with cutovers planned in waves so delivery never stops. We also handle GitLab licensing and resale.
What are the exit terms on a managed retainer?
60-day notice after the 12-month minimum. Exit includes a 30-day shadow period where your team takes the pager, with us on Slack. Documentation, Terraform, runbooks, and dashboards stay with you — they were always yours.
Expansion bay · CloudBooster
cloudbooster.io →
Production-grade infrastructure without the DevOps hire.
A governed path for creating and changing AWS infrastructure — proposal, checks, approval, apply, audit trail.
Design partners onboardingNight shift · lamp on
Thirty minutes.
One architect.
No deck.
You bring the problem and the constraints. We bring an opinion, a sketch, and an honest estimate. If we are not the right fit we will say so on the call.
- 00:00Intro & contextYour situation, current AWS / GitLab setup.
- 00:05The problemConstraints, what you have already tried.
- 00:15Sketch & optionsOpinion on the table, risks called out.
- 00:25Estimate & fitShape, timeline, ballpark — and whether we are right for it.
- 00:30Recap & next stepThe sketch in your inbox, plus a clear yes/no on fit.
Reply within 1 business dayEET (UTC+2 / +3)NDA: Mutual, on requestinfo@tidora.io
Senior engineers on the pager — ops desk, hall TLN-01