Book a call

07— Product engineering

Cloud architecture for products and AI workloads

Central Dev designs and builds cloud architecture for web products and AI workloads, sized for what you actually run. The work covers new products, migrations from other hosting, and cost and reliability reviews.

Because we also build the applications that run on it, we design infrastructure around the real product. That includes its data, its traffic and, for AI features, where the models run.

01— What we build

Infrastructure sized for your workload

Cloud architecture for web products and AI workloads that is reliable, cost-aware and sized to the workloads you actually run.

EDGEAPPDATACDN · firewallZone AZone BreplicationprimaryreplicaIllustration: an example multi-zone layout
FIG. 07  An example cloud layout: two zones behind one edge layer, with the database replicated across them.
  • 01

    Cloud architecture for new products

    A cloud setup that fits the product you are launching and leaves room to grow, rather than one copied from a much larger company.

  • 02

    Migrations from other hosting providers

    A planned move from a single server or another host to the cloud, designed to keep disruption for your users to a minimum.

  • 03

    Infrastructure for AI workloads

    AI models running inside your own cloud account, so AI workloads operate alongside the rest of your product.

  • 04

    Cost and reliability reviews

    A review of your current setup, where the cost comes from and what is most likely to fail, with the changes worth making.

02— Where it fits

For products that outgrew their first setup

Who it is for

  • Startups moving from a single server to a reliable cloud setup
  • Teams with a growing cloud bill and no clear explanation for it
  • Companies that want AI workloads to run inside their own cloud account

When another service fits better

When the issue sits in the application rather than the infrastructure, we say so. A slow or costly system is sometimes fixed in the code, not in the cloud.

03— Client work

No published case study for this service yet

Our named client work to date is listed below, shown with each client's permission.

  • AdjustedAI agent · CRM · Web app · Mobile appDelivered
  • Entera ToolsCRM · MVPIn progress
  • Tucano Coffee MoldovaDigital menuDelivered

On an introductory call, we can explain how this work relates to your project.

Read the case studies

04— How it starts

How an engagement starts

It starts with an introductory call about your current infrastructure and what needs to change. Scope, estimate and timeline are agreed with you afterwards.

  1. 01

    Introductory call

    A 30-minute conversation about what you run today, where it is hosted and what is not working.

  2. 02

    Project discussion

    We review your current setup together and agree whether the work is a new build, a migration or a review.

  3. 03

    Agreement and NDA

    We sign an NDA and agree the engagement model, scope, estimate and timeline with you.

  4. 04

    Kickoff

    Work starts on the date we agree together.

  • Ongoing product work

    Dedicated team

    A team of Central Dev engineers working exclusively on your product, within your tools and processes.

  • Defined scope

    Fixed price

    A defined scope, an agreed price and a clear list of deliverables, all set before work begins.

  • Evolving scope

    Hourly (time & materials)

    You are billed for the hours worked, and priorities can change as the product evolves.

05— FAQ

Questions about cloud architecture

Answers to common questions about this service. For anything not covered here, book a call or email us.

Email us

What does a cloud architecture engagement cover?

It covers infrastructure for new products, migrations from other hosting, AI workloads and reviews of cost and reliability. We agree with you on the introductory call which of these your project needs.

Can AI workloads run inside our own cloud account?

Yes. AI models can run inside your own cloud account, alongside the rest of your product.

Can you reduce our cloud costs?

We start with a review of your setup rather than a promised saving. We assess what you run and where the cost comes from, then recommend the changes worth making and the ones that are not.

What is included in a cost and reliability review?

A review of your current setup, its main cost drivers and its most likely points of failure. The result is a set of recommended changes, which our team can also implement.

Book a call

07— Start a project

Let's review your cloud setup

Book a 30-minute introductory call or describe your current setup by email. Scope, estimate and timeline are agreed with you after the first conversation.

Book a call

Choose a 30-minute slot on Cal.com. Times are shown in your own time zone.

  1. 01Choose a time slot and add a few lines about your project.
  2. 02Discuss your goals, constraints and the right engagement model with our team.
  3. 03Agree scope, estimate and timeline together.

Prefer email?

Describe your project in a few lines, and we will continue the conversation by email.

Hours
09:00–19:00 Moldova time