Service 05 of 10 · Technology & Intelligence

Cloud set-up that keeps your systems and AI fast, reliable and affordable.

We set up and run the cloud servers behind your apps and AI, for business owners and IT heads. We keep speed, cost and time online within agreed targets.

A live dashboard for an example set-up called your-platform-prod, with illustrative values. Six servers with GPUs (the chips that run AI) are about 68 per cent busy, with two spares ready. Full response time is about 842 ms, against a 1.5 second target. It produces 18.4 thousand tokens (pieces of words) per second. Cost is $1.21 per thousand requests, against a $1.45 budget. Three regions show their share of traffic and how clean their power grid is.

Typical length
4–12 weeks per phase
Clouds
AWS · Azure · Google Cloud
Standard
Targets and budgets from day one

02Cost and speedboth grow with every word

Where AI bills and delays surprise teams.

AI is billed and timed per token, a piece of a word. Most overspend is waste: growing prompts, unlimited retries and idle GPUs (the chips that run AI).

Anatomy of one request

A support answer grounded in your documents

Cost per 1k of this request
$22.20
baseline
Time to first token
0.62 s
baseline
Monthly · 1.5M req
$33,300
baseline
Tokens, rate and cost for each part of one request
PartTokensRate per 1MCost
System prompt & tools 1,200 $3.00 $0.0036
Retrieved context 3,800 $3.00 $0.0114
User input 150 $3.00 $0.0005
Output 450 $15.00 $0.0068
Per request5,600$0.0222

Time to first token is reading time: the model reads all the input first, so long prompts wait longer.

Tokens per second is writing speed: the answer streams out steadily, so long answers take longer.

Screens marked Illustrative are examples, not client results. Example prices per million tokens: $3 in, $0.30 cached in and $15 out. Illustrative

This is one costly request: an answer from your documents. Across all features, the example averages $1.21 per 1,000 requests.

Showing the request as shipped: 5,600 tokens, $22.20 per thousand of this request, 0.62 seconds to first token.

  • 01

    Growing prompts

    Each turn resends the whole chat and document extracts. Turn 12 can carry 7 times the text of turn 1.

    FixSummarise the chat, trim extracts and reuse the fixed instructions.

  • 02

    Unlimited retries

    3 automatic retries on a slow provider can bill one answer up to 4 times, and slow it further.

    FixLimit and space out retries, and switch to a backup provider.

  • 03

    Idle GPUs between peaks

    GPUs sized for evening peaks run at a tenth of capacity overnight, at full cost.

    FixAdd GPUs as the queue grows, switch them off when quiet and run bulk jobs at night.

03How it fits togetherapps → gateway → models → data

Our standard design grows with demand and fails safely.

Every AI request passes one gateway you own: a single link to all your models. It picks the model, caps spend and switches provider if one fails.

  1. 01

    Your apps

    Websites, apps, staff tools, AI agents and scheduled jobs all call one internal AI link.

  2. 02

    Access control

    Checks who is calling, logs every call (OIDC, JWT) and sets usage limits per customer.

  3. 03

    AI gateway

    Picks the model by cost, speed, quality and data type. Switches provider if one fails, reuses answers and caps each team’s use.

  4. 04

    AI models

    Pay-per-use models from several providers, plus open models on vLLM in your cloud. GPUs are added or removed as demand changes.

  5. 05

    Testing new models

    A new model answers copied traffic unseen, then a small live share. It stays only if quality, speed and cost hold.

  6. 06

    Data and storage

    A search index so AI can answer from your documents, plus storage for models, files and logs.

  7. 07

    Checks across every part

    Monitoring with OpenTelemetry. Keys locked in Vault or a cloud key store. Rules as code for access, networks and where data stays.

  • Fastest to start

    Pay-per-use AI models

    Choose when

    • Use is low or uneven
    • You need the strongest models today
    • Nobody on the team runs GPUs

    Watch forPrices at high volume, provider usage limits and how they treat your data.

  • Most control

    Open models you host

    Choose when

    • Steady use makes your own GPUs cheaper
    • Data must stay in your account or in India
    • You need top speed or a custom-trained model

    Watch forGPU supply, on-call cover and updates.

  • Our default

    Both, behind one gateway

    Choose when

    • One AI link for every team
    • Picks by cost, speed and data type
    • Switches when a provider fails

    How we run itIts rules are code, reviewed and tested like the rest.

Model swaps

Swap a model in days, without a rebuild.

Every request goes through the gateway, so a new or cheaper model is a settings change. We test it on your own examples first.

  1. Day 1New model added to the gateway · tested on your own examples
  2. Day 2Copied traffic · answers scored, never shown
  3. Day 35% of traffic · speed, cost and errors watched
  4. Day 5Goes live, or undone in one change

Technologies we work with

04Failure drilla planned failure, in a safe window

Failure drills that test recovery before an outage does.

Pick a failure and add it to 10 minutes of realistic traffic. Run it with the safeguards off, then on. Compare speed, errors and the error budget.

Source code on a dark monitor in a dim room lit by a red and blue glow
Rehearsed in advanceDrills run in working hours from a step-by-step fix guide, so night calls follow a rehearsed plan.Photo: Jakub Żerdzicki / Unsplash

Interactive failure drill. Choose one of three injected failures, turn the resilience patterns on or off, then press Play or move the timeline slider. Four charts show successful requests per second, p95 latency, error rate and the error budget left for the month; the architecture map shows which component failed and where traffic goes; the incident log lists what happened and when. All values are illustrative.

Inject

10:00/ 10:00

Successful requests req/s

39

60 0

p95 latency ms

888 ms

SLO 1.5 s ≥ 4 s 0 ms

Error rate %

0.08%

100.0% 0.00%

Error budget left % of month

62.0%

65.0% 40.0%

Architecturegpu-node-3 ejected · replica added

Incident log8 events

  1. Drill started · 40 req/s at peak · p95 860 ms
  2. gpu-node-3 stops responding (injected)
  3. Health check fails 3 × 3 s → node ejected from the pool
  4. In-flight requests retried once on healthy nodes
  5. Queue depth 180 · backpressure on · p95 1.3 s
  6. Autoscaler: +1 replica from the warm pool
  7. Replica ready · weights loaded from local cache
  8. Recovered without a page · budget used 0.03%
Peak client-visible errors
4.0%
Peak p95 latency
1.38 s
Error budget used
0.03% of the month
Fast-burn page
Not triggered

  • The target

    99.9% online each month

    That leaves 0.1% of requests free to fail: 43.2 minutes of full downtime in a 30-day month. This allowance is the error budget. Your team decides how to spend it.

  • The alert

    An alert when the budget drains

    The alert calls an engineer if the budget drains fast: 2% of the month’s budget in an hour. A slow drain opens a ticket.

  • The safeguards

    What “on” switches on

    • Checks that take failed servers out
    • A gateway that switches to a backup provider
    • A queue that holds excess requests, and limited retries
    • Reused answers and spare servers on standby
    • Automatic switch to a backup region

05Faster, cheaper AIthe same answers, on fewer GPUs

4 ways to run AI models faster and for less.

Each one runs the same model on less GPU time. It goes live only after a test on your own examples shows quality has held.

  • 01

    Continuous batching

    2–4× the requests per GPU

    A scheduler with six GPU lanes, each decoding a request at about 75 tokens a second, 450 tokens a second between them, and a queue of three waiting requests. As a lane finishes, the next queued request joins the batch at once; a fixed batch would hold the queue for another 5.8 seconds.

    The GPU handles many requests at once. A new one joins when a slot frees, without waiting for the slowest.

    Quality check quality 0.94 → 0.94 · reply time −38% · pass

  • 02

    Prompt caching

    replies start 53% sooner

    Two requests shown as rows of twelve token blocks. The first request computes every block. The second request shares the same seven-block prefix, which is served from the cache, and only computes the five new blocks.

    The fixed instructions and examples repeat on every call. We keep them ready, so only the new text is read.

    Quality check quality 0.94 → 0.94 · first word 0.62 s → 0.29 s · pass

  • 03

    Quantisation

    50–75% less memory

    8B model · one 24 GB GPU

    Weights
    8 GB
    4k-token seqs
    ~28
    Decode
    1.6×
    Golden set
    0.93

    FP8 selected: 8 bits per weight, 8 gigabytes of weights on a 24 gigabyte GPU, room for about 28 concurrent 4,000-token sequences, 1.6 times decode speed, golden-set score 0.93, inside tolerance, ships.

    The model is stored in fewer bits (FP8 or INT4), leaving room for more requests. The quality check measures any loss.

    Quality check −0.01 · inside the 0.02 tolerance · ships

  • 04

    Speculative decoding

    45–60% less writing time

    A draft model proposes four tokens at a time. The target model checks all four in one pass, keeps the accepted ones and adds one token of its own; the rest is discarded. The output line grows by the accepted tokens: twelve tokens take three target passes instead of twelve.

    A small model guesses the next few words and the main model checks them in one step. Same answer, sooner.

    Quality check same output by design · writing time −56% · pass

Engines we run models on

These engines update monthly. We load-test each one and run the quality check on a few servers before live traffic.

  • vLLM PagedAttention · continuous batching · prefix caching
  • NVIDIA TensorRT-LLM in-flight batching · FP8 · speculative decoding
  • SGLang RadixAttention prefix cache · structured output
  • Ray Serve multi-model serving · autoscaling replicas
  • Hugging Face open-weight models · TGI

Gains are typical ranges for chat and answers from documents. They depend on the model, prompts and traffic. Illustrative

068 layersfrom GPUs at the bottom to security at the top

Your AI set-up, from GPUs to security.

Each layer has one job, one owner and its tools. Open one to see what it holds and what we decide with you.

U08 · tray open0 critical CVEs

Security & policy

Vault or the cloud key store gives each service short-lived passwords, so none is saved in code. We scan software before release, watch it while it runs and block anything unsafe or unsigned.

Technologies we work with here

  • Vault
  • Trivy
  • Falco
  • Snyk
  • OPA Gatekeeper
  • Kyverno

Decided with you at this layer

  • Short-lived access instead of fixed keys
  • Only signed software in production
  • Models, prompts and logs treated as sensitive data

U07 · tray open14 SLO alerts

Monitoring & costs

OpenTelemetry tracks every request from gateway to GPU, with its size, reused answers and cost. Any slow or costly request points to its feature, team and model.

Technologies we work with here

  • OpenTelemetry
  • Prometheus
  • Grafana
  • Datadog
  • PagerDuty
  • OpenCost

Decided with you at this layer

  • Standard AI tracking on every model call
  • Alerts when the budget drains
  • Daily spend per team and feature

U06 · tray open31% cache hits

AI gateway

Every AI request passes through it. It checks access, picks the model, switches on failure, reuses answers and caps team budgets.

Technologies we work with here

  • Kong
  • Cloudflare
  • Redis
  • LiteLLM
  • Envoy AI Gateway

Decided with you at this layer

  • Which data may leave the country
  • Backup providers and time limits
  • When saved answers can be reused

U05 · tray open12.4M vectors

Data & search

Good answers from your documents need fast, complete search. We size the index for speed and update it within minutes of a change.

Technologies we work with here

  • Qdrant
  • PostgreSQL
  • Milvus
  • Apache Kafka
  • pgvector

Decided with you at this layer

  • Search tuned to find the right passages
  • Re-index only what changed
  • Each customer’s data kept apart

U04 · tray open3 models live

AI models

Open models run on vLLM or TensorRT-LLM behind a standard API, so the gateway treats them like pay-per-use ones. Copies are added as the queue grows.

Technologies we work with here

  • vLLM
  • NVIDIA
  • Hugging Face
  • Ray
  • SGLang
  • Triton

Decided with you at this layer

  • Which model and settings for each route
  • Prompt caching and batch limits
  • Scaling on the waiting queue

U03 · tray open6 node pools

Kubernetes & code

GPU servers are kept for AI work. Terraform builds the cloud, Helm packages the apps and Argo CD keeps each cluster matched to the code. Nothing live is changed by hand.

Technologies we work with here

  • Kubernetes
  • Helm
  • Terraform
  • Argo
  • Docker
  • Karpenter
  • KEDA

Decided with you at this layer

  • GPU servers with one spare ready
  • Test systems switched off when unused
  • Every change reviewed before it goes live

U02 · tray open3 regions · 2 in India

Cloud & regions

We build on the cloud you already use, in regions your data rules allow. A secure base sets log-ins, networks, logs and security rules once. A web firewall and caching sit in front.

Technologies we work with here

  • AWS
  • Microsoft Azure
  • Google Cloud
  • Cloudflare

Decided with you at this layer

  • Primary and standby regions
  • Reserved, pay-as-you-go and spot servers
  • Private links to AI providers where offered

U01 · tray open8 × L40S · 68%

GPUs & AI chips

We pick the smallest chip that fits the model and your traffic. An 8B model at FP8 suits an L4 or L40S. 70B models and long inputs need an H100 or H200. Inferentia and TPU are tested on your traffic first.

Technologies we work with here

  • NVIDIA
  • L4 · 24 GB
  • L40S · 48 GB
  • H100 · 80 GB
  • H200 · 141 GB
  • AWS Inferentia2
  • Google Cloud TPU

Decided with you at this layer

  • GPU type for each model and input size
  • Reserved base, pay-as-you-go peaks, spot for bulk
  • GPUs kept 60–80% busy
A data-centre switch with direct-attach cables plugged into its high-speed ports
U01 · the networkGPU servers share data over fast links. A slow network leaves fast GPUs waiting.

Where data stays

Cloud regions we use in India

The gateway sets where data goes. Personal data cannot go to a model or region outside India. Bulk jobs on other data may run in cheaper, lower-carbon regions.

Cloud regions in India for keeping data local
CloudRegionLocationCode
AWSAsia Pacific (Mumbai)Maharashtraap-south-1
AWSAsia Pacific (Hyderabad)Telanganaap-south-2
Microsoft AzureCentral IndiaPunecentralindia
Microsoft AzureSouth IndiaChennaisouthindia
Google CloudMumbaiMaharashtraasia-south1
Google CloudDelhiDelhi NCRasia-south2

GPU supply varies by region and changes often. We check it before a design is final.

07Cloud costscost per request · per team · forecast · spikes

Cost per request, visible before the invoice.

Every AI request is tagged with its feature, team and route, so you see what each one costs. An AI agent checks costs daily. A named person approves any change it suggests.

finops · your-platform · September · month to date

Illustrative
Spend to date
$26.3k
day 19 of 30
Forecast
$41.8k
± $2.9k at 80%
Budget
$45.0k
7% headroom
Cost per 1k requests
$1.21
−14% vs August
Unallocated
3%
of spend without a tag

Unit cost

Cost per 1k requests against the cost model

Cost per 1k requests against the cost model, with target and change against last month
NameAgainst targetActualTargetTrend
Support assistant412k requests $1.42 $1.60 −12%
Document search1.1M requests $0.38 $0.50 −4%
Sales email drafts58k requests $2.94 $2.20 +31%
Invoice extraction96k documents $0.71 $0.90 −9%
Internal copilot203k requests $1.18 $1.20 +2%

Spend forecast

$k · cumulative

Month-to-date spend of 26.3 thousand dollars on day 19, forecast to reach 41.8 thousand dollars by day 30, with an 80 percent range of 38.9 to 44.6 thousand, under a budget of 45 thousand.

GPUs in use against reserved capacity

last 7 days · 2 h buckets

Over seven days, serving used an average of 5.4 of 8 reserved GPUs, about 68 percent. 4 afternoon peaks rose above the reservation onto on-demand GPUs, and nightly batch jobs ran on 4 spot GPUs for 168 GPU-hours.

  • 5.4 avgserving on reserved · 68% of the reservation
  • 4 peaksburst to on-demand
  • 168 GPU-hbatch on spot, about 65% cheaper

Anomaly · yesterday 01:00–03:10

+$1,240 vs forecast

Embedding job re-ran 3×

embed-docs-nightly timed out listing the object store and retried the whole job instead of the failed batch, three times over.

Proposed by finops-agent · confidence 0.92

jobs/embed-docs.yaml
-  retries: 3
+  retries: 1
+  retryScope: batch
+  idempotencyKey: "{{ .source.version }}"

Awaiting your approval · the agent cannot merge

  1. finops-agentAnomaly: embedding spend 3.1× forecast (z = 4.2)
  2. finops-agentCause: 3 full re-runs after an object-store timeout
  3. finops-agentFix proposed · awaiting human approval
  • Cost reports per team

    The gateway labels all AI use and GPU time by feature and team. Each team sees its costs weekly, before finance sees the total.

  • Reserved, pay-as-you-go and spot

    Steady work runs on reserved servers and peaks on pay-as-you-go ones. Bulk jobs run on cheap spare capacity (spot) and save progress, so an interruption costs minutes.

  • Off when idle

    Test and preview systems switch off outside working hours. The first request after that waits for start-up, so live systems never switch off.

Cost standards we work to

  • FinOps FrameworkFinOps Foundation · inform, optimise, operate
  • FOCUSFinOps Open Cost and Usage Specification · one bill format for every cloud

08Sustainabilitycarbon per request, measured and cut

AI carbon emissions, cut by scheduling.

The same job emits more or less carbon depending on when and where it runs. Live requests stay near users. Bulk work moves to cleaner hours and regions your data rules allow.

scheduler · your-platform · tomorrow

A chart of grid carbon intensity across one day for Mumbai and Chennai, both highest overnight and in the evening and lowest around midday, when solar output peaks; Chennai sits lower throughout. The embedding refresh is scheduled in the shaded four-hour window.

Inferencelatency-sensitive · stays near usersall day

Embedding refresh4 h · 22 kWh · drag the block or use the slider11:00–15:00

Backup snapshotfixed · keeps the RPO02:00 · 14:00

Grid intensity, I
465g/kWh
Job emissions
12.1kgCO₂e
SCI per 1k documents
30.3gCO₂e
−33% vs the 01:00 Mumbai cron

SCI = ((E × I) + M) per RE 22 kWh · I 465 g/kWh · M 1.9 kg · R 1k documents

Both regions are in India, so documents stay in the country. Carbon figures here are examples; live ones come from grid data and GPU energy readings. Illustrative

09Reliabilitytargets · error budgets · on-call

Reliability targets we set with you, and an error budget we track.

Time online is a target you choose and pay for. We agree it with you, and the error budget decides when to release features and when to fix things.

slo · your-platform-prod · rolling 30 days

Availability

Successful responses ÷ all responses, measured at the gateway, excluding client 4xx.

Objective
99.9%
over 30 days
Observed
99.96%
this window
Budget
43.2 min
total for 30 days
Remaining
25.8 min
59.7% of budget

An error-budget burn-down for Availability across thirty days, falling from the full budget to 59.7% remaining, plotted against a straight ideal-burn line, with deployment markers along the bottom and one step drop where an incident burned budget quickly.

One provider incident on day 12 burned 6.4 minutes. The multi-provider router carried the rest of the traffic, so the budget survived it.

p95 latency

Share of non-streaming requests completed end to end within the target, per endpoint class.

Objective
99% < 1.5 s
p95 observed 1.21 s
Observed
99.38%
this window
Budget
345k req
total for 30 days
Remaining
131k req
37.9% of budget

An error-budget burn-down for p95 latency across thirty days, falling from the full budget to 37.9% remaining, plotted against a straight ideal-burn line, with deployment markers along the bottom and one step drop where an incident burned budget quickly.

A day-20 release raised p95 by 340 ms. Fast burn paged on-call inside the hour, the release was rolled back, and the budget is being repaid before the next feature ships.

Time to first token

Share of streaming responses that put their first token on the wire within the target.

Objective
95% < 800 ms
p95 observed 612 ms
Observed
96.8%
this window
Budget
965k streams
total for 30 days
Remaining
623k streams
64.6% of budget

An error-budget burn-down for Time to first token across thirty days, falling from the full budget to 64.6% remaining, plotted against a straight ideal-burn line, with deployment markers along the bottom.

Prompt caching and continuous batching hold first token steady through the evening peak, so the budget burns close to the ideal line.

How alerts work

A fast burn (14.4× the safe rate for an hour) calls the on-call engineer. A slow burn (6× over 6 hours) opens a ticket for the next working day. Alerts track what users feel, not single servers.

The freeze rule

With under 25% of the budget left, releases stop and the next 1- or 2-week cycle goes on reliability. We agree this in advance, so nobody argues it during an outage.

Illustrative figures

The window, targets and limits are the ones we use. The plotted values are sample data for an example system. Illustrative

  • Fix guides for every alert

    Written during the build, each guide gives the first 5 commands, the dashboards to open and how to undo.

  • A shared on-call rotation

    A main and a backup engineer, a clear escalation path and handover notes at each shift. Your engineers can join the rotation.

  • No-blame reviews after outages

    Within 5 working days: what happened, why, what monitoring missed and who fixes what, planned into the next cycle.

  • Tested disaster recovery

    Recovery time and data-loss limits are set per system. Each quarter, a timed rebuild from code and backups tests them.

A network patch panel in close-up, its ports numbered and grey and blue cables plugged into them
02:40 · on-callEach alert links to its fix guide, so on-call starts with a plan.

Standards we build to

The security, continuity and server standards we build to. Certifying your own systems is a separate project we can prepare you for.

  • ISO/IEC 27001:2022Information security management systems
  • SOC 2Trust Services Criteria
  • CIS Controls v8.1Critical Security Controls and Benchmarks
  • NIST CSF 2.0Cybersecurity Framework
  • ISO 22301:2019Business continuity management systems

Support hours are agreed per project (business, extended or 24×7) and written into the fix guides with who to call.

10How it worksmeasure · design · build · run

Measure first, then cut delays, downtime and cost.

We measure speed, downtime, spend and carbon first, so you can check every change against them. We fix what the numbers point to, not what looks old. Weeks shown are typical.

  1. 01

    Measure

    Wk 01–02

    We map how things run today and measure traffic, speed, outages, spend and carbon. Then we agree targets with you.

    • Today’s numbers
    • Agreed targets
    • Cost breakdown
  2. 02

    Design

    Wk 02–04

    We design the new set-up, the capacity you need and how to move across. We write down each decision and why.

    • New set-up design
    • Capacity plan
    • Written decisions
  3. 03

    Build

    Wk 04–10

    We build the set-up as code and test it under heavy load. Monitoring and cost tracking start on day one.

    • Set-up as code
    • Load test results
    • Dashboards
  4. 04

    Run

    Wk 10–12

    We switch traffic over and write the fix guides. A monthly review of targets, spend and capacity sets the next fixes.

    • Fix guides
    • Monthly reviews
    • Cost report

The 3 numbers a phase is judged on

Measured on your traffic before the first change and after each release. Bars show the cut from the starting figure. One example project shown. Illustrative

  • Chat reply time (p95)

    2.9 s 1.21 s

    −58%

    Continuous batching, prompt caching and sending short requests to a smaller model.

  • Cost per 1,000 requests

    $2.95 $1.21

    −59%

    Servers matched to demand, quantised models and caching, with bulk work on reserved capacity.

  • Idle GPU hours a week, test systems

    96 h 12 h

    −88%

    Test and preview systems switch off outside working hours.

After launch, reviews continue. Each month we review the error budget, outages and costs per request. Before busy seasons, we check capacity.

11What you getyour set-up as code, in your accounts

Everything we build is saved as code in your accounts.

What we make for you is yours once it is paid for. Tools we already had stay ours, and you get a free, permanent licence to use them.

A browsable listing of the infrastructure repository handed over at the end of the engagement, with 9 files you can open: Terraform for the GPU pool and the residency policy, Helm values for model serving and the AI gateway, a Grafana cost dashboard, the SLO objectives with their burn-rate alert rules, the GPU node-failure runbook, a k6 peak-load profile and the disaster-recovery drill script.

your-platform-infra — main

Arrow keys move, → opens a directory, ← closes it, Enter shows a file.

terraform/envs/prod/main.tf

module "gpu_pool" {  source = "../../modules/gpu-pool"   region        = "ap-south-1"    # Mumbai, primary  instance_type = "g6e.2xlarge"   # 1 × L40S, 48 GB  min_nodes     = 6  max_nodes     = 10              # 6 serving + 2 warm + 2 burst  warm_nodes    = 2  taints        = ["nvidia.com/gpu=present:NoSchedule"]  tags          = local.cost_tags # feature, team, model route}

11 linesPR #482 · platform · plan attached, 26 policy checks passed

Open any file to see what is inside. Paths and values are examples. You get the structure and the maths behind the limits. Illustrative

Handover pack

  • Server set-up as codeTerraform · Helm
  • Diagrams and written decisionsDiagrams · records
  • AI model hosting set-upContainers · config
  • Automatic test and releasePipelines · Argo CD
  • Targets, dashboards & alertsGrafana · alert rules
  • Load and outage test reportsk6 · report
  • Cost and carbon report per teamDashboard · spreadsheet
  • Change goes through reviewEvery change is reviewed, with a plan, an automatic rules check and a named approver. Nothing goes live from a laptop.
  • Your accounts, your keysCloud accounts, code stores, password stores and AI keys are yours from day one. We work inside them with limited, logged access.
  • Decisions are written downShort records explain what we chose, what we rejected and what would change our mind.

Built and run with

  • Terraform
  • Helm
  • Kubernetes
  • Argo
  • GitHub Actions
  • Vault
  • Grafana
  • k6

12Outcomeschecked monthly, the same way each time

5 numbers, measured every month.

We agree these targets and how to measure them at the start. Each monthly review shows every reading with its evidence, misses included.

monthly review · your-platform · September 4 of 5 inside the agreed band · 1 out, with an owner

  • Chat reply time (p95)

    99 per cent of chat replies inside the agreed time, measured for each type of request.

    1.21 s was 1.34 s Inside the objective

    0 s agreed band 0–1.5 s 3 s

    Set for each type of request and held under load tests at forecast peak, not guessed from average traffic.

  • Cost per 1,000 requests

    Within ten per cent either side of the cost model agreed at forecast volume.

    $1.21 was $1.41 On the cost model

    $0.00 agreed band $1.17–$1.43 $2.40

    Tracked per feature and per team, so a price rise or a prompt that grew shows up as a line, not a surprise invoice.

  • GPU utilisation at peak

    Between 55 and 75 per cent at the daily peak — busy enough to be economic, with headroom left.

    81% was 68% Above the band

    0% agreed band 55–75% 100%

    Below the band you pay for idle GPUs. Above it, queues build and the slowest replies get much slower.

    Why it missed, and what happens next. A launch in week 3 tripled one feature’s traffic. More GPUs are being added and scaling now starts sooner. The owner and date are in the review log.

  • Carbon per 1,000 requests

    Lower each quarter against a ceiling agreed at the start of it, measured the same way each time.

    26.4 g was 29.8 g Trending down

    0 g agreed band 0–32 g 60 g

    Carbon falls with the same levers as cost: batching, caching, quantisation, and batch work scheduled into cleaner hours.

  • Error budget spent

    No month where the error budget runs out without a decision behind it.

    40.3% was 52% Inside the allowance

    0% agreed band 0–60% 100%

    A planned burn during a migration is a decision. An unplanned one is a design or a monitoring gap, and it gets a review.

  • 01

    Speed on target

    Each feature gets a speed target, even for its slowest answers, tested under peak traffic.

  • 02

    Reliability you can quote

    Agreed targets and an error budget. When it runs low, fixes come before features.

  • 03

    Spend each team can see

    Each team sees the cost per request, user and AI model it controls, so it can cut it.

Ranges and readings are sample data, including the miss. Your targets come from your own starting numbers in the first phase. Illustrative

Offers & plans

Pick the cloud services you need, alone or combined.

We cover cloud set-up, app hosting, AI models, reliability and cost. Each offer says who it suits.

Categories
04
Offers
16
Plans
04
Not sure what you need? Tell us the problem

How to buy

  1. 01Pick offers. Ask about one, or add several to one enquiry.
  2. 02Choose a plan. A small job, a fixed project or ongoing help.
  3. 03Send your enquiry. We reply within one working day.

Browse by category

Timelines are typical. We write the scope before we quote.

01Cloud set-up & migration

4 offers
Typical timeline: 8–20 weeks

Cloud migration

We move your apps and data to AWS, Azure or Google Cloud in planned stages, with little downtime.

What’s included

  • Mapping what connects to what
  • Move, update or rebuild each app
  • A staged plan you can undo
  • Switch-over and launch support
  • AWS
  • Azure
  • Google Cloud
  • AWS
  • Microsoft Azure

Best forTeams leaving their own servers or cutting down to one cloud.

Typical timeline: 4–8 weeks

Cloud foundations

A secure start in the cloud. We set up accounts, networks, log-ins, logs and rules as code before your apps move in.

What’s included

  • Account and network structure
  • Single sign-on and minimal access
  • Security rules built to CIS Benchmarks
  • Central logs and cost labels
  • Secure start
  • Rules as code
  • CIS Benchmarks
  • AWS
  • Microsoft Azure

Best forTeams new to the cloud, or tidying a set-up that grew unplanned.

Typical timeline: 2–3 weeks

Cloud set-up review

We check your current set-up for reliability, security, speed and cost, and rank what to fix.

What’s included

  • Checked against cloud best practice
  • Risk and cost findings
  • Recommended new design
  • Ranked plan of fixes
  • Best practice
  • Fix plan
  • AWS
  • Microsoft Azure

Best forTeams preparing for growth, an audit or a funding round.

Typical timeline: 2–6 weeks

Global site speed

We serve your site, files and app data from servers near your users, with caching and a firewall against attacks.

What’s included

  • Caching near users
  • Code near users
  • Firewall and bot blocking
  • Speed checks by region
  • CDN
  • Firewall
  • Global

Best forSites and apps with users spread across regions.

02App hosting & releases

3 offers
Typical timeline: 6–12 weeks

Kubernetes hosting

A Kubernetes set-up for live apps that adds servers as demand grows, with security rules and releases from code.

What’s included

  • Cluster set-up on EKS, AKS or GKE
  • Releases from Git with Argo CD
  • Auto-scaling and resource limits
  • Secret keys, network rules and scans
  • Kubernetes
  • Git-based
  • Scales itself

Best forTeams running many services, or outgrowing simple hosting.

Typical timeline: 8–16 weeks

Developer self-service

Ready-made templates so your engineers can create, test and release apps the approved way, without waiting on another team.

What’s included

  • Approved service templates
  • Automatic release with security checks
  • Previews of changes
  • Developer portal and guides
  • Service templates
  • Self-service
  • DORA metrics

Best forEngineering teams whose releases are slowed by manual steps.

Typical timeline: 3–8 weeks

Automatic testing & release

We automate testing and release, and set up your servers as code, so test and live systems match.

What’s included

  • Build, test and release steps
  • Terraform or Pulumi modules
  • Sign-off before changes go live
  • Undoing a release
  • CI/CD
  • As code
  • Repeatable

Best forTeams releasing by hand or with fragile scripts.

03Running AI models

4 offers
Typical timeline: 4–10 weeks

AI model hosting

We run AI models on your own servers or as pay-per-use services, tuned so answers come fast and cost less.

What’s included

  • vLLM, Triton or pay-per-use AI
  • Batching, quantisation and caching
  • Picking models by cost and quality
  • Load tests against speed targets
  • vLLM
  • Speed
  • Cost per request

Best forProducts with steady AI use, strict data rules or tight speed needs.

Typical timeline: 3–8 weeks

GPU servers

GPUs sized to your work, well scheduled and switched off when idle.

What’s included

  • Choosing GPU type and number
  • GPU groups and scheduling
  • Spot and reserved capacity plan
  • GPU use dashboards
  • GPU
  • Off when idle
  • GPU use

Best forTeams training or running AI with rising GPU bills.

Typical timeline: 6–12 weeks

Model releases

Repeatable steps to train, test, version and release models and prompts. Every release can be traced and undone.

What’s included

  • Experiment logs and a model library
  • Training and indexing steps
  • Quality checks before each release
  • Versioned models and prompts, with undo
  • Model library
  • Traceable
  • Repeatable

Best forData teams moving models from experiments to live use.

Typical timeline: 4–8 weeks

Private AI in your cloud

We run open models such as Llama, Mistral or DeepSeek in your own cloud or data centre. Sensitive data stays under your control.

What’s included

  • Model selection and licence check
  • In your cloud or data centre
  • Access control and logging
  • Cost compared with pay-per-use AI
  • Open models
  • Data stays local
  • Access control

Best forRegulated sectors and teams with strict data-location rules.

04Reliability, cost & carbon

5 offers
Typical timeline: 4–8 weeks

Monitoring & alerts

See how your live systems behave and fix problems before customers notice. We set targets, track requests and send only useful alerts.

What’s included

  • Targets and error budgets
  • Request tracking with OpenTelemetry
  • Alert tuning to cut noise
  • Fix guides and outage reviews
  • Targets
  • OpenTelemetry
  • Error budgets

Best forTeams who hear about outages from customers first.

Typical timeline: 3–6 weeks, then monthly

Cutting cloud costs

We find and cut wasted cloud spend and show each team its costs, without slowing anything down.

What’s included

  • Costs labelled by team
  • Servers sized to demand, idle ones off
  • Savings plans, reserved and spot servers
  • Monthly cost report per team
  • Sized to demand
  • Cost per unit
  • Savings plans
  • AWS
  • Microsoft Azure

Best forCompanies whose cloud bill grows faster than their revenue.

Typical timeline: 2–4 weeks

Load testing

Find out how much traffic your system can handle, and what breaks first, before a launch or peak.

What’s included

  • Tests based on your real traffic
  • Load, spike and soak tests
  • Finding weak points
  • Capacity plan
  • k6
  • Capacity
  • Weak points

Best forTeams expecting a launch, sale or seasonal peak.

Typical timeline: 4–8 weeks

Backup & disaster recovery

We make sure you can recover from outages, deletions or ransomware, with recovery targets per service tested in drills.

What’s included

  • Recovery time and data-loss limits
  • Backups copied to a second region
  • Standby set-up
  • Restore and recovery drills
  • RTO · RPO
  • Built to ISO 22301
  • Drills
  • AWS
  • Microsoft Azure

Best forBusinesses where downtime or data loss would be costly.

Typical timeline: 3–6 weeks

Lower-carbon computing

We measure your software’s carbon and cut it along with cost. We use the Green Software Foundation’s Software Carbon Intensity (SCI) method.

What’s included

  • Carbon per request, measured first
  • Cleaner regions and times for work
  • Fixes that cut cost and carbon
  • Reporting for sustainability teams
  • SCI
  • Carbon per request
  • Green IT

Best forOrganisations with sustainability targets or reporting duties.

Your enquiry

Tick “Add to enquiry” on any offer, choose a plan, then continue. Or enquire about one offer.

How we work with you

Ways to start, from a question to a quote.

Ask a quick question, send your project details or request a quote. The person who will lead the work reads each one in full. Services in your enquiry go with it.

Or book a 30-minute call

What are you sending?

  1. 01

    About 2 minutes3 short answers

    For a first chat, a press request or anything not ready to plan yet.

    You get A reply from a named lead

  2. 02Recommended

    About 8 minutes5 short steps

    Goals, who it is for, budget and timing, so our first reply can outline the work.

    You get Options and prices after one call

  3. 03

    About 15 minutesYour documents attached

    Your documents, deadlines and the purchasing and security rules to meet.

    You get Confirmation and a named lead

How it is priced

Each plan shows how it is priced. Work starts once we agree a written scope and price.

  • Typical length
    1–3 weeks
    Pricing
    Fixed fee
  • Typical length
    3–9 months
    Pricing
    Fixed price per stage
  • Typical length
    Ongoing · 6-month minimum
    Pricing
    Monthly fee
  • Typical length
    6–18 months
    Pricing
    Priced per written scope
Compare what each plan includes
What each plan includes and who it suits
PlanWhat you getBest for
SprintA short, fixed job that answers one clear question.
  • Scope and result agreed before we start
  • A senior lead and the right specialists
  • A weekly review with you
  • A clear answer or a test version
An audit, a brand check or a test version of an app
MilestoneA bigger build in stages you approve and pay for one at a time.
  • Stages, each with its own scope and approval
  • A go or stop review at each stage
  • Re-plan between stages as you learn
  • Pay for each stage you approve
Work too big for one contract, such as a large app
RetainerA monthly team that runs and improves what we built.
  • Team time set aside for you every month
  • Agreed response times for requests and fixes
  • A monthly review and a to-do list
  • Planned improvements, not only fixes
Monthly social media and ads, or care for live sites and apps
EnterpriseA large, long project with its own team and agreed response times.
  • A project director and a decision group
  • A team for each part of the work
  • Response times, reports and a list of risks
  • Security, legal and purchasing checks in the plan
Large companies making changes across markets, brands or business units

13Questionsanswered plainly

Cloud set-up, your questions answered.

Short answers on hosting, reliability, cloud choice, capacity, cost and carbon.

  • 01 Host our own AI models, or pay per use?

    Pay per use is fastest to start and cheapest at low volume. Hosting your own open models pays off with steady, high volume, strict data-location rules or tight speed needs. We work out the break-even on your traffic first.

  • 02 What is a reliability target and error budget?

    A target such as 99.9% of requests answered within 0.8 seconds over 30 days. The error budget is the 0.1% left over: about 43 minutes of downtime in a 30-day month. When it is spent, fixes come before new features.

  • 03 Which cloud do you recommend?

    The one that fits your contracts, data rules, skills and AI needs. We work with AWS, Azure and Google Cloud. Where it is worth the cost, we build so you can switch later.

  • 04 How do you reduce GPU costs?

    We match servers to demand and do less work per request. We batch and cache requests, shrink models and send simple requests to smaller models. Where the work allows, idle servers switch off and jobs run on cheaper capacity.

  • 05 Do you measure carbon?

    Yes, per request, with the Software Carbon Intensity (SCI) method. The fixes that cut cost also cut carbon.

  • 06 Do you work out how many servers we need?

    Yes, from your own traffic. We plan the Kubernetes cluster, server groups for each kind of work and GPU sharing. The plan shows what happens at peak and what spare servers cost.

Tell us what you need built.

You will talk to the lead who would run your work.

Book a call

Three ways to start

We always agree a written scope and price before work begins.

Choose one of the three ways above