Allan Simões AdegasPortuguês
Menu
Back to home

The Soil Company · Software Engineer (Full Stack and Cloud) · 2026 – now

Cloud migration for an agtech startup

The Soil's agronomic consulting platform was growing on infrastructure that was expensive and had no clear owner. I led the full migration and took ownership of the Google Cloud infrastructure, organizing projects, access and resources. The cloud bill dropped by about 30%.

≈ 30%
lower cloud costs
1
clear owner of the infrastructure
Full stack
Python backend and React frontend

Context

The Soil is an agronomic consulting agtech: consultants follow clients, farms and seasons through the platform. For a startup, every dollar spent on cloud competes with product.

The challenge

Migrate without stopping consultants' work, and come out the other side with infrastructure that someone understands, controls and can afford.

What I built

Leading the migration
I planned and ran the full move of the infrastructure to Google Cloud.
Organization and governance
Projects, access and resources organized for reliability, governance and cost control, with a clear owner.
Product day to day
Beyond the cloud, I'm one of the main developers of the platform, on the backend (Python) and frontend (React), and I build automations and service integrations.

Architecture

Architecture: Cloud migration for an agtech startupPrevious infra → Migration. Migration → Reliability. Migration → Governance. Migration → CostBeforeGoogle CloudPrevious infracostly, no clear ownerMigrationled by meReliabilityresources organized by projectGovernanceaccess with a clear ownerCost≈ 30% lower
Conceptual view of the migration.

Decisions and trade-offs

One owner for the infrastructure
Infrastructure without an owner accumulates cost. Taking ownership mattered as much as the technical side of the migration.
Cost as a requirement
For a startup, cloud cost is a product requirement, not an operations detail.

Results

  • About 30% lower cloud costs.
  • Infrastructure with an owner, organized access and traceable resources.
Monthly cloud cost, as an index (before = 100).

Approximate figure, comparing monthly cost before and after the migration.

What I'd do next

  • Infrastructure as code and per-project budget alerts.
  • Google Associate Cloud Engineer certification, in progress.

Stack

Google CloudPythonReactAutomações e integrações