Skip to content
Amarello
Cloud, data and governance

A cloud and data foundation ready to operate, and ready for the AI that comes next.

We design, migrate, modernize and operate cloud infrastructure. We grew up building on Google Cloud, which is our primary and best-validated runtime environment today; the team is also certified on AWS. One team answers for the architecture, the cost and the operation.

Why it happens

The options a buyer usually has fall short in specific places.

  1. 01

    The cloud was purchased, but never designed

    Projects that grew without a common foundation: no central identity, no network rules, no cost tags. Each team solved things on its own.

  2. 02

    The migration moved servers, not the operation

    What was in the data center was moved as it was. Costs went up, agility never arrived, and nobody was left in charge of optimizing it.

  3. 03

    The data is not ready for AI

    Scattered sources, with no governance and no measured quality. AI pilots are left without reliable data to move into production.

How we solve it

From diagnosis to operations, with the same team.

Five stages, each with deliverables and acceptance criteria. We start with the workload that carries the most risk or the most cost, not with everything at once.

  1. 1

    Diagnosis

    Inventory of workloads, dependencies, costs and risks. What should be migrated, modernized, left where it is or retired.

  2. 2

    Architecture and foundations

    Landing zone, networking, identity, security and infrastructure as code, in one cloud or several.

  3. 3

    Migration

    In waves, with testing and a rollback plan: servers, databases and virtualized environments.

  4. 4

    Modernization

    Containers, microservices, APIs and continuous delivery, where the business justifies it.

  5. 5

    Operations and FinOps

    Observability, continuity, cost under control and support with SLA by priority.

Services

What we do in the cloud, by service line.

The technologies listed are the ones we have worked with. We do not start from the tool: we choose with your team what the case needs.

  • Architecture and cloud foundations

    Project organization, networking, identity and access, and infrastructure as code. Hybrid and multi-cloud architecture.

    • Landing zone
    • Infrastructure as code
    • Hybrid cloud
    • Multi-cloud
  • Migration

    Moving workloads from a data center or from another cloud, by lift and shift or by adapting the applications to the new platform: servers, databases and virtualized environments.

    • Compute Engine
    • VMware Engine
    • Cloud Spanner
    • Databases
  • Application modernization

    Containers and Kubernetes, microservices, API strategy and management, and continuous delivery with built-in security.

    • GKE
    • Anthos
    • Apigee
    • DevSecOps
  • Data and analytics

    Lakehouse, data engineering, dashboards for the business and models in production with their monitoring.

    • BigQuery
    • Looker
    • Lakehouse
    • MLOps
    • Vertex AI
  • Security and governance

    Identity- and context-based access, protection of sensitive data, security posture and multi-cloud governance.

    • BeyondCorp
    • Security Command Center
    • reCAPTCHA Enterprise
    • Multi-cloud governance
  • Operations and FinOps

    Cloud operations team, proactive monitoring, disaster recovery and continuous cost optimization.

    • Observability
    • Disaster recovery
    • FinOps
    • Managed services
Why us

What we do offer.

  • More than 150 implementations since 2008 with companies in any industry, many of them regulated and high-volume.
  • Google Cloud Services Partner of the Year in 2023 and 2024; team certified on Google Cloud and AWS.
  • The same team designs, migrates and operates: whoever proposes the architecture answers for it in production.
  • Total cost on the table from the diagnosis, with assumptions and a range. Cost control is part of the operation.
  • The foundation is left ready for AI: governed data, role-based access and traceability.
  • The exit is written into the contract: infrastructure as code, documentation and handover to your team.

Criterion by criterion

Integration with existing systems
Architecture and migration designed around your workloads and their dependencies.
Quality and acceptance criteria
A diagnosis per workload and disaster recovery with agreed, tested objectives.
Total cost
Total cost with assumptions and a range; continuous review against real consumption.
Operations and support
Dedicated team, SLA by priority and 24/7 for critical incidents.
Continuity and handover
Infrastructure as code and documentation; exit written into the contract.
Proof

Numbers before adjectives.

Since2014

designing, migrating and operating cloud for enterprises

2023 · 2024

Google Cloud Services Partner of the Year

Airlines

Aeroméxico

Amarello's published case reports a 146% higher conversion rate and USD 170,000 in incremental revenue during the first month.

Read the full case study

Banking

Actinver

An API and container layer connected existing systems. Google Cloud reports that the share of response time attributable to transactional systems went from 90% to 10%.

Read the full case study

Media

El Universal

The Google Cloud case study reports up to 40% time savings on tasks previously performed manually.

Read the full case study

Insurance

GNP

App Engine and Firebase as the framework for agile development of portals and web services, and Spanner as the transactional database for critical applications. More agile services and high-availability schemes.

Read the full case study

Consumer goods

Alquería

BigQuery and Data Fusion replaced a legacy on-premise data platform: reports 100 times faster for the commercial area, a first machine learning sales forecast model and savings on BI licenses.

Read the full case study

Retail

Cochez

Data platform migration from another public cloud to Google Cloud: Data Fusion and BigQuery integrate financial, operational, inventory and customer sources; Vertex AI covers the predictive models' lifecycle.

Read the full case study

Other sectors

Navent

The entire data architecture migrated to Google Cloud in six months: BigQuery as the cornerstone, Cloud Composer for orchestration and Data Fusion for ETL. Analytics 3 times faster and a lighter operational load.

Read the full case study

Insurance

Inter.mx

Migration with native Google Cloud tools and elastic, secure resources: Cloud SQL, Cloud Storage and load balancers protected by Cloud Armor, with monitoring and alerting. Service visibility improved 100%.

Read the full case study

Financial services

Broxel

A central repository in BigQuery with sources integrated through Change Data Capture, orchestrated processes with Composer and Data Fusion, and Looker for end users. More than 60 users with fresh, governed data.

Read the full case study

Banking

Banco Davivienda

Looker Studio and BigQuery dashboards that integrate real Google Workspace usage data and the organization's directory: more than 20,000 users in six countries, with real-time information to focus actions.

Read the full case study

Financial services

Financiera Independencia

Compute Engine for computing, Cloud SQL for data models on managed schemas, BigQuery and Firebase: an upgraded platform, agility to enable services and savings in infrastructure costs.

Read the full case study

Financial services

Apoyo Económico

Migration and re-engineering of the risk portfolio's analytical processes, from a licensed relational database to BigQuery: from several days to a couple of hours, with real-time dashboards for the business areas.

Read the full case study

Media

Organización Editorial Mexicana

More than 40 news sites, 2.5 million users per month and more than 17 million visits on containers and Cloud SQL on Google Cloud, with close to 100% availability.

Read the full case study

We have worked with

  • Actinver
  • Abanca
  • Banca Mifel
  • Banco Azteca
  • Banorte
  • Banregio
  • CIBanco
  • Citibanamex
  • Compartamos Banco
  • Covalto
  • Davivienda
  • HSBC

Banking · Insurance · Media · Airlines · Telecom

How it is implemented

We move phase by phase, with verified results.

We start with a bounded process, agree on what success means, and prove the result before scaling.

  1. 1

    Diagnosis

    Weeks, depending on scope

    What we do
    Inventory, dependencies, current cost and risks. A recommendation per workload: migrate, modernize, leave or retire.
    What you provide
    Read access, an owner per system and the current invoices.
  2. 2

    Foundations and first wave

    Depends on complexity

    What we do
    Landing zone, identity and security, and the first workload in production as proof of the model.
    What you provide
    Change windows and a technical counterpart.
  3. 3

    Migration and modernization

    In waves

    What we do
    Successive waves with testing, a rollback plan and acceptance criteria per workload.
    What you provide
    Users for testing and the owners of each application.
  4. 4

    Operations

    Continuous

    What we do
    Observability, continuity, cost control and support with SLA. Documented handover to your team.
    What you provide
    An operations owner on the business side.
For your technical team

Architecture, integrations, security and deployment.

Clouds

Google Cloud Platform (GCP) is our primary runtime environment. The team is also certified on Amazon Web Services (AWS); private and hybrid infrastructure depending on the case. We tell you what is validated in your environment before proposing it.

Infrastructure as code

The environment is defined in versioned code: networking, identity, policies and workloads. What is deployed can be audited and reproduced.

Containers and APIs

Managed Kubernetes, service mesh and API management with security policies, quotas and consumption analytics.

Data

Lakehouse, pipelines with measured quality, catalog and lineage. Models with monitoring in production.

Security

Identity- and context-based access, encryption, secrets management, monitored security posture and protection layers on sensitive data.

Continuity

Disaster recovery plan with agreed, tested recovery time and recovery point objectives.

Costs

Tagging, budgets and alerts from day one; periodic review of sizing and committed-use discounts.

Exit

Infrastructure as code, documentation and handover to your team, written into the contract.

Frequently asked questions

What we get asked before we start.

Do you still work with Google Cloud?

Yes. We grew up building on Google Cloud and were recognized as Services Partner of the Year in 2023 and 2024. Today it is our primary and best-validated runtime environment and we keep designing, migrating and operating on it. What changed is the starting point: we begin with the process and choose with your team what the case needs.

Our cloud is AWS, Azure or our own data center. Can you work there?

The team is also certified on AWS and we work with private infrastructure. Before proposing anything we tell you what we have validated in your environment and what would need to be validated during the diagnosis. We will not tell you we run on every cloud without having tested it.

Do we have to migrate everything?

No. A cloud migration project starts with the diagnosis, which recommends per workload: migrate, modernize, leave where it is or retire. We start with one bounded wave with acceptance criteria and move wave by wave, with verified results.

What happens to cost after migrating?

Cost is designed before migrating: tagging, budgets, alerts and sizing. Once in operation it is reviewed periodically against real consumption. The diagnosis delivers an estimated cost with assumptions and a range, compared against what you pay today.

Who handles a failure outside business hours?

For critical incidents there is a response team with 24/7 coverage, defined times by priority for mitigation and restoration, and four escalation levels up to the CTO.

How do I know I will not end up dependent on Amarello?

The exit is written from the start: infrastructure as code, documentation, access and handover to your team. Before closing production, your team carries out a significant change with our support.

Tell us where your infrastructure stands today.

We start with a bounded scope, agree on what success means, and prove the result before scaling.

We use one necessary cookie and, only if you accept, measurement cookies to understand how the site is used. No advertising. Cookie policy