Cloud Infrastructure PlatformClient work

Several clouds. One customer experience.

The platform gives customers one place to choose, order and manage servers across infrastructure providers. VTS built the client’s platform, connecting its server catalog, provisioning, customer console and automation interfaces.

VTS scope

Platform build, provisioning, customer console

Client
Not disclosed
Industry
Cloud infrastructure
Status
Live
Architectural cutaway illustration of cloud infrastructure, with server rows and blue network connections.Illustration
Architectural cutaway illustration of cloud infrastructure, with server rows and blue network connections.

The challenge

What needed to change.

Choosing infrastructure can mean comparing unfamiliar plan names, regions and hardware across several provider consoles. The client needed to make that choice manageable in one product.

01

Confusing consoles

Choosing a server means decoding plan names, regions and hardware specs.

02

One vendor's limits

Regions, hardware and pricing all depend on whichever provider a host is built on.

03

Connected operations

Ordering, access, billing and support need to stay connected after the server is provisioned.

The engineering decision

One console, several clouds behind it.

The platform sells servers from more than one infrastructure provider, but customers see one catalog, one console and one bill. Each provider names its plans, regions and hardware differently, so we built an adapter layer that maps every provider into one set of server families and regions. A customer picks a plan and a region, and the platform provisions it on whichever provider fits, without the customer ever needing to know which one. The cost is upkeep: every new provider means another adapter to build and keep in sync.

What VTS delivered

From decision to delivery.

The whole path from browsing plans to running a server.

01

Configuration catalog

Six compute families, from shared CPU to GPU, priced by region.

02

Customer console

Servers, usage, snapshots and access in one place.

03

Ordering and provisioning

A plan and a region become a running server.

04

Team roles

Server access kept separate from billing.

05

API and webhooks

Automation for scripts and services.

06

Docs, status and trust center

Quick start, API reference, live service status and security policies.

The product flow

  1. 01

    Choose a plan and a region.

  2. 02

    Add an SSH key.

  3. 03

    The server provisions.

  4. 04

    Manage it from one console.

Project facts

Platform scope

6
compute families described
Project scope
API
and webhooks for automation
Delivered capabilities

Shared CPU, dedicated CPU, CPU-optimized, general-purpose, high-memory and GPU configurations. Availability depends on the selected provider and region.

Working together

How we engaged.

VTS built the platform for the client, from the marketing site and catalog to provisioning and the customer console.

Your next project

Building a SaaS or infrastructure platform?

We build platforms that keep the hard parts out of your customers' way.

Start a project