Tidora · Tallinn — senior crew, production AWS

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.

Reply within 1 business day · NDA: mutual, on request

Partner statusAWS Advanced Tier Services
DeliveryGitLab Partner
BaseTallinn · EET (UTC+2/+3)
CrewSenior engineers only

A boutique cloud team helping Baltic and CEE innovators migrate and scale with confidence.

NORDLINE Veriton Kalda&Co PAGUS helix. SAAREMA

Outcomes
that matter.

Stencilled on the side of every engagement: the number that moved, and what moved it.

10–40%

Lower AWS costs

Lower AWS costs after right-sizing, modernization and FinOps governance.

AWS resellCostFinOps
<1MIN

Cutover downtime

Cutover downtime target for carefully planned cloud and GitLab migrations.

Phased wavesRollbacksRunbooks
20–50%

Faster delivery

Faster software delivery with GitLab CI/CD, IaC, Kubernetes and platform engineering.

GitLab CI/CDTerraformK8s
24/7

Managed operations

Managed cloud operations available for production AWS and Kubernetes environments.

MonitoringIncidentSLA

59°26′N 24°45′E

Ships have harbors. Your infrastructure has us.

A harbor is deep water, working cranes, and a berth with your name on it. For companies that run on AWS, that is what we keep open.

Berth
manifest.

Five lines of work. Each one scoped, staffed and signed — pick a berth.

01Berth 01 · Infrastructure

AWS Cloud Infrastructure & Modernization

Secure, scalable, production-grade AWS environments — designed, built and modernized by senior engineers.

Project · 8–20 weeks
  • AWS landing zones & multi-account architecture
  • Kubernetes-EKS, networking, security & compliance
  • Infrastructure as Code: Terraform & Crossplane
  • Migration, modernization & performance optimization
Plan your platform
02Berth 02 · Delivery

GitLab, DevOps & Platform Engineering

Faster, safer software delivery on GitLab — resale, implementation, migration and developer-platform engineering.

Project · 6–14 weeks
  • GitLab resale, implementation & migration
  • GitLab CI/CD, DevSecOps pipelines & runner architecture
  • Repository & pipeline migrations (GitHub, Jenkins, Bitbucket)
  • Kubernetes deployment workflows & developer platforms
Modernize delivery
03Berth 03 · AI & Data

AI & Data Solutions on AWS

Practical AI engineering on solid cloud foundations — built into real products, not slide decks.

Pilot · 4–8 weeks
  • Amazon Bedrock, RAG systems & AI assistants
  • Data pipelines, data architecture & personalization
  • AI integration into SaaS products & workflows
  • Secure environments & production deployment
Scope an AI pilot
04Berth 04 · Commercial

AWS Resell & Cloud Cost Optimization

Better commercial terms backed by senior cloud engineering — not a discount-only relationship.

Ongoing · no lock-in
  • AWS resale & consolidated billing
  • Savings Plans & Reserved Instance guidance
  • Cost reviews, FinOps & budget governance
  • Architecture optimization & technical advisory included
Review your bill
05Berth 05 · Operations

Cloud Operations & Managed Services

Reliable day-to-day operation of AWS, Kubernetes and GitLab-based delivery environments — senior engineers on the pager.

Retainer · 12-month min · 60-day exit
  • 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
Hand us the pager

SLAs are written into the MSA, not the brochure.

Contract · not a sales line

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.

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.

Owners — Principal · Cloud Architect
Phase 02Week 3–8+

Foundation & Build

Landing zone, IaC, pipelines — built by the pod, demoed weekly, no clickops.

Owners — Tech Lead · 2–4 Senior Engineers
Phase 03Ongoing

Steady State

We take the pager, or we hand it over — 30-day shadow period, runbooks and dashboards included.

Owners — SRE Lead · Account Engineer
“Tech scale-up cut migration downtime from days to minutes — unlocking 30% faster feature delivery.”
Recent engagement · Baltics

Shipped
cargo.

What we shipped, who shipped it, and the number that moved.

Manifest 01 — VilniusSeries B fintech · 180 engineers
68%Spend ↓ YoY

“Cut AWS spend 68% without slowing delivery.”

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 engineerKarl Tamm
ResultSpend ↓ 68% YoY
Manifest 02 — TallinnMobility platform · 70 engineers
11Days · DO → AWS

“Off DigitalOcean and into AWS in 11 days.”

One pod, one weekend cutover, full Terraform handover. They kept their CI green the whole time.

LeadLiisa Nõmm
Duration11 days
Manifest 03 — RigaEuropean healthtech · 110 engineers
8→0P1 / quarter

“From two outages a quarter to zero, in six months.”

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.

P1 incidents8 → 0 / quarter
MTTR94 min → 19 min
LeadJanis Ozols

Ways to
engage.

Four shapes of contract. Fixed scope or named engineers on the pager — nothing in between.

DiscoveryT-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-scopeT-02

Project SOW

One defined workstream — built, shipped and handed over. Fixed price, fixed deliverables, signed SOW.

4–10 weeks
Signed SOW
Scope a project
Most picked
ProgramT-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
RetainerT-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
Handover clause

Documentation, Terraform, runbooks, and dashboards stay with you — they were always yours.

The crew
on shift.

Six names. No bench, no juniors, no subcontracted on-call.

Karl TammPrincipal Cloud Architect AWS SAP · DevOps Pro11Y
Liisa NõmmMigration Lead AWS SAA · Security8Y
Janis OzolsSRE Lead AWS DevOps Pro · CKA9Y
Mart SaarPrincipal Engineer AWS SAP · Database12Y
Eglė RagelisSenior Cloud Engineer AWS SAA · Security7Y
Andris BērziņšDevOps Engineer AWS DevOps Pro6Y

Rotation staffed from Tallinn & Riga · EET (UTC+2/+3)

Straight
answers.

The questions a skeptical CTO asks before the first call — answered the way we answer on the call.

F-01Where 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.

F-02What 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.

F-03What 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.

F-04Do you do Azure or GCP?

AWS is our primary cloud platform — that’s where we hold our Advanced Partner status and where we lead green-field work. We will integrate with workloads sitting in Azure or GCP, but we do not lead green-field projects on those platforms. Our GitLab practice runs across whichever cloud the customer prefers.

F-05Can 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.

F-06What 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.

senior engineers on the pager

Dispatch office · intro call

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.

You will hear a ballpark on the first call, not after three meetings.

Departures — Intro callBoarding
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 day EET (UTC+2 / +3) NDA: mutual, on request info@tidora.io
Book a 30-min call