Backend & DevOps · AWS · Terraform · Kubernetes · Plovdiv, Bulgaria (EU)

Backend & DevOps engineering for fintech and SaaS teams.

I'm Hristo Boyarov. 12+ years of professional experience, these days building and operating AWS infrastructure as code: Terraform, Kubernetes, CI/CD, monitoring. Alongside it, I develop backends in Node.js and PHP. One of the infrastructures I run is regulated under DORA. VGravity is the core: the infrastructure as code that supports everything on top of it. I work B2B, on my own or embedded in your team.

  • 12+ yearsprofessional experience
  • Severalproduction AWS infrastructures under management
  • DORAone regulated fintech platform among them
  • Weeklybackups restore-tested automatically
  • Any hourimmediate response to critical incidents

The usual situation

Most of this work starts from the same place.

Deploys are manual and depend on one person. Monitoring is the client emailing that something is not working. The AWS bill keeps growing and nobody is sure why. Staging doesn't exist, so changes are tested in production. Secrets live in a .env file that gets passed around in chat. A customer or an auditor sent a security questionnaire two weeks ago and it is still open. Nobody remembers the last time a backup restore was actually tested - and nobody dares to upgrade the database.

If part of that sounds familiar, this is the work I take over.

Services

What I do

01 / infrastructure

Cloud infrastructure & DevOps

I build AWS environments as code and keep them in good shape.

  • Terraform for the whole infrastructure: network, compute, databases, storage, IAM
  • Compute sized to the need: ECS with Fargate as the simple start, Kubernetes (k3s or EKS) when the workload calls for it
  • CI/CD with GitHub Actions, including image scanning that blocks deploys on critical vulnerabilities
  • Monitoring with Prometheus, Grafana, Loki and Tempo, alerts defined as code
  • AWS budget configuration, with notifications for incidents and cost thresholds on the channel you use: email, Slack, SMS or anything else
  • DNS and mail configuration: records as code, DKIM, SPF and DMARC set up properly
  • Backups with scheduled, automated restore verification
  • DORA: I run a regulated infrastructure today and can map your controls against the regulation

Good fit if: you run on AWS, it mostly works, and “mostly” is the problem.

02 / backend

Backend systems

APIs and services in Node.js/TypeScript and PHP. I've been doing this for 12 years.

  • Payment integrations: Stripe, PayPal, ledgers, reconciliation jobs
  • Financial systems: double-entry ledgers, monitoring and reporting, incident detection and reports
  • REST and RPC APIs with Symfony, Laravel or Express, documented and tested
  • Real-time features with Socket.IO and Redis
  • Event-driven services on SQS/SNS where the complexity is justified
  • Database design on PostgreSQL and MySQL: schemas, constraints, transactions, replication
  • Integrations with Google, Slack, Mailchimp, SendGrid, OpenAI, Anthropic and other services

Good fit if: the product is growing faster than the backend.

03 / operations

Ongoing operations

I keep systems running and I answer when they break.

  • Monitoring that reaches a person, not just a dashboard
  • Immediate response to critical incidents, any day, any hour
  • Patching, upgrades, backup checks, budget alerts and cost review
  • Small improvements shipped continuously instead of piling up

Good fit if: nobody on the team owns production.

End to end

Full solutions: from backend to infrastructure

You don't need one company for the code and another for the servers. I develop the backend in Node.js or PHP, design the AWS infrastructure it runs on, wire the CI/CD pipeline, set up monitoring, backups and budget alerts, and then operate the whole thing. One point of responsibility, one contract, and no gap between development and operations - which is where most problems usually live.

  • Backend: Node.js · PHP
  • Infrastructure: Terraform · AWS
  • Kubernetes or Fargate
  • CI/CD · monitoring · backups
  • Ongoing operations

Process

How we work

  1. Email

    Write a few lines about the project and the services you need - through the form below, or directly to [email protected]. I reply within one business day.

  2. Meeting

    We arrange a 30-minute meeting to discuss it further, free. You describe the system and the problem, I ask questions, and we decide whether it makes sense to work together.

  3. Estimate

    For existing systems, usually an audit first, estimated in hours up front. For new builds, a written proposal with scope, milestones and a number.

  4. Build

    In your AWS accounts and your repositories from day one. Everything as code, built on the VGravity core - the Terraform, Kubernetes and CI/CD foundation I reuse and adapt for every setup. I use AI tooling to speed up the process and keep code quality high; the responsibility for what ships stays with me. A short written update every week.

  5. Operate or hand over

    Either I stay on and run it, or you get documentation, runbooks and a walkthrough call. In both cases you own everything.

Pricing

Pricing

Simple model: one setup package with a fixed quote between €3,000 and €8,000 depending on scope, and €36 per hour for everything else. Prices excluding VAT.

Production infrastructure setup

€3,000-€8,000fixed quote, in writing

A complete production environment on AWS, built as code and handed over documented. Where you land in the range depends on what the setup includes; after the intro meeting you get a fixed number in writing.

  • Terraform for the whole infrastructure: VPC, networking, security groups, load balancer with TLS
  • Container registry (ECR) with vulnerability scanning on push
  • CI/CD pipeline in GitHub Actions: test, build, scan, deploy; deploys blocked on critical findings
  • AWS budget configuration, with spending and incident notifications on the channel you use: email, Slack, SMS or anything else
  • Backups to S3
  • Documentation and a handover call

Around €3,000 - the simple start

ECS on Fargate, CloudWatch monitoring and alerts, S3 backups. No cluster to operate, no nodes to patch. Right for one normal web application running only on AWS.

Up to €8,000 - the full setup

A production-ready k3s Kubernetes cluster with autoscaling workers, Prometheus, Grafana and Loki monitoring, a structured audit log stream, managed PostgreSQL or MySQL with a verified restore test, DNS configuration, mail configuration with DKIM, SPF and DMARC, and a staging environment.

Scope: the quote lists exactly what is included; anything beyond it is billed at €36/hour. Typical duration: 2-5 weeks depending on scope.

Not included: changes to your application code beyond deploy wiring, and your AWS bill itself.

Everything else

€36 / hourestimated before I start

One rate for all work outside the setup package. You get a written estimate before I start, and a report of hours with every invoice.

  • Backend development in Node.js and PHP, integrations and fixes
  • Infrastructure audits: a full review typically takes 20-30 hours
  • Migrations, DORA gap work and one-off projects
  • Ongoing operations: monitoring I personally answer, patching, upgrades, backup checks and cost review
  • Immediate response to critical incidents, any day or hour. The monthly minimum of 10 hours covers the on-call commitment; cancel with 30 days' notice

Every engagement starts with an email about the project, followed by a free 30-minute meeting.

About

Who you're hiring

Hristo Boyarov

Hristo Boyarov, in Plovdiv, Bulgaria.

I've been building for the web for over 15 years, the last 12 professionally. Full-stack work at a web studio. Four years leading backend at a medical fundraising platform: architecture, payments, real-time systems. Three years on event-driven microservices on AWS for large-scale platforms. Independent since 2024. Right now I maintain several production AWS infrastructures built with Terraform and running Kubernetes; one of them operates under DORA.

I keep the setup small on purpose. You talk to the person who writes the code and gets the alerts. When a project needs frontend or design, I bring in people I've worked with for years: a React developer and a UI/UX designer, under one contract.

B2B only · Plovdiv, Bulgaria · EU VAT invoices · NDA on request

  • Cloud & infrastructureAWS (EC2, ECS, Lambda, RDS/Aurora, S3, CloudFront, SQS/SNS, IAM/KMS), Terraform, CloudFormation, Kubernetes (k3s), Docker
  • CI/CD & observabilityGitHub Actions, Prometheus, Grafana, Loki, Tempo, OpenTelemetry
  • BackendNode.js / TypeScript, PHP (Symfony, Laravel), REST & RPC APIs, Socket.IO, Redis
  • DataPostgreSQL / Aurora, MySQL, Redis

FAQ

How do you charge?

€36 per hour, excluding VAT. Larger pieces of work get a written estimate before I start, and every invoice comes with a report of hours. The production infrastructure setup is a fixed-price package between €3,000 and €8,000, depending on what it includes. Operations clients have a monthly minimum of 10 hours, which covers the on-call commitment.

Do you work with existing teams, or only solo?

Both. Often I handle infrastructure and backend foundations while the in-house team ships product. I've led backend teams, and I've also been the only backend developer on a project.

What does “immediate response” mean exactly?

For clients on an operations agreement: critical incidents get a response right away, any day, any hour, weekends included. Everything else within one business day. What counts as critical is agreed in writing at the start, so it isn't debated during an outage.

How do contracts and invoicing work?

B2B, with a standard services contract and an NDA if you need one. Invoices come from my company in Bulgaria with EU VAT. For EU companies, reverse charge applies: a 0% VAT invoice against your VAT number.

Which time zone are you in?

EET (UTC+2/+3). Full overlap with European working hours, and with the US East Coast until early afternoon. Most communication is written; calls when they're actually needed.

Will we be locked in to you?

No. Work happens in your cloud accounts and your repositories from day one. Infrastructure is code, decisions are documented, and handover is part of the job, not a separate negotiation.

Can you take over an existing system that has grown organically?

Yes. That's what the audit is for: I map what exists, what's risky and what it costs, and we fix things in order of priority.

Do you do frontend or full product builds?

My own work is backend and infrastructure. For UI I bring a React developer and a designer I've worked with for years, under the same contract, so you still have one point of responsibility.

What about DORA specifically?

I operate infrastructure for a regulated EU financial entity today. Controls are mapped to the regulation article by article, incidents are classified in the logs, and the platform produces its own evidence: tested restores, CI gates, audit trails. If DORA applies to you, an audit includes a gap map against it.

Do you use AI in your work?

Yes, daily. I use AI tools to optimize processes and keep code quality high: reviews, tests, catching regressions, automating the repetitive parts. What ships is still my responsibility, and client code is handled under the contract and NDA.

Do you handle on-premise?

Yes. I've configured Proxmox VE with Kubernetes for a client, and I build hybrid setups across providers - for example DigitalOcean together with AWS.

Contact

Let's talk about your system.

Write a few lines about the project and the services you need - through the form, or directly by email. I reply within one business day, usually faster, and then we arrange a meeting to discuss it further.

The message didn't go through.

Please email me directly at [email protected] and I'll answer personally.

Thanks, got it.

I'll reply within one business day. If it's urgent, email me at [email protected].