Skip to content
GraniteBolt, Home

Cloud infrastructure you can read, rebuild and afford.

We audit what you run and what it costs, capture it as infrastructure as code, and set up deployments any engineer can trigger. Migrations are planned workload by workload, with a rollback at every step, and a person reviews every change before it is applied.

What we build

  • 01

    Cloud and cost audit

    A written report on security, reliability and spend, with the top fixes ranked by savings and risk.

  • 02

    CI/CD pipeline

    Every change tested and deployed the same way, with previews for pull requests and a one-step rollback.

  • 03

    Infrastructure as code

    Your existing cloud captured as code, so it can be reviewed, reproduced and changed safely.

  • 04

    Migration

    Servers or a hosting provider moved to the cloud, workload by workload, with a cutover plan and a rollback.

  • 05

    Monitoring and backups

    Alerts that reach a person, dashboards for what matters, and backups that have been restored at least once.

What you receive

  1. 01A written audit or migration plan, with risks, costs and rollback steps
  2. 02Infrastructure as code in your repository, reviewed as a plan before every apply
  3. 03CI/CD pipelines with tests, previews and rollback
  4. 04Monitoring, alerts and backups, with a tested restore
  5. 05Least-privilege access, secrets in a manager, and a security review
  6. 06Runbooks, a recorded walkthrough and 30 days of fixes

Stack

Our cloud work is on AWS, with Cloudflare at the edge where it helps.

  • AWS
  • Terraform
  • AWS CDK
  • GitHub Actions
  • Cloudflare
  • Docker
  • CloudWatch or Grafana

Typical timeline

Migration · 3-6 weeks
  1. 01Audit
  2. 02Plan and code
  3. 03Migrate workloads
  4. 04Cutover

Phases are typical. The date in your quote is the one we commit to.

How we scope it

A written fixed quote within 48 hours of your first message or call.

  • Cloud and cost audit

    Written report and ranked fixes

    5 business days

  • CI/CD and infrastructure as code

    Pipelines, plus your cloud as code

    2-3 weeks

  • Migration

    Up to 3 workloads

    3-6 weeks

  • Each extra workload

    Added to a migration

What shapes the quote

  • The number and complexity of workloads
  • Downtime limits and data volume
  • Compliance and data-residency requirements
  • Legacy systems that cannot be containerised
  • Several accounts or regions

Ways of working

Most engagements are fixed-scope projects: numbered deliverables, a fixed price and a fixed date, all in writing before work starts. Product builds run as focused sprints with a working demo every week. After handover, Run keeps a system monitored, updated and improving month by month. The first call settles which one fits, and the quote states it in writing.

The AI angle

Run AI in your own cloud

Model calls through your own cloud account and region where the provider offers it, with logging and cost alerts from the first day.

See AI solutions

Questions about this service

Do you work with Azure or Google Cloud?

Our cloud work is on AWS, where we can review every change with authority. For Azure or Google Cloud we will say so plainly and, where useful, refer you to someone we trust.

Will a migration cause downtime?

We plan for none and agree the acceptable window in writing. Every workload gets a rehearsal, a cutover plan and a rollback step.

Who has access to our cloud accounts?

Named people with least-privilege roles, for the length of the project. Access is removed at handover and you keep the audit trail.

What counts as a workload?

One application or service with its data: a website, an API with its database, a background worker. A migration covers a set number; each extra one is an add-on.

  • API and system integrations

    Your systems agree with each other, with retries, logs and alerts built in.

    Typical
    2-4 weeks

    See how we build it

  • Web apps and SaaS MVPs

    A first version of your product, live with real users on a fixed date.

    Typical
    20 business days

    See how we build it

  • Custom business software

    Internal tools and portals shaped around how your team actually works.

    Typical
    2-4 weeks

    See how we build it

Tell us what you need built.

Describe it in plain words. Within 48 hours you have a written fixed quote and a delivery date.

A written, fixed quote within 48 hours.

Or write to hello@granitebolt.com

Your time and ours

Calls seven days a week

  • Beirut

  • Dubai

  • Riyadh

  • Doha

  • Kuwait City

  • Manama

  • Muscat

  • Cairo

  • Berlin

  • London

  • New York

Beirut shares the working day with Dubai, Riyadh, Cairo, Berlin and London, and the afternoon overlaps the New York morning.