Skip to main content

Damascus → MENA + global

Production platforms, custom products, and mobile.Clear hand-back to your team.

We deliver senior-led software for production. Our work spans multi-cloud platforms and reliability (including deep AWS, GCP, and Cloudflare engineering), ShaDaSoft products we build and operate, mobile applications, and applied AI when the problem warrants it and risk is handled deliberately. We integrate the toolchain and services you already depend on.

Named senior owners, written scopes, and exit criteria come with every engagement, along with runnable documentation, structured transfer sessions, and an explicit off-ramp when your team is ready to take over. Damascus-led delivery with MENA and EU on-call windows when you need pager coverage.

How we partner

Senior-led work with explicit boundaries, before anyone touches production.

  1. Scope you can sign

    Written statements of work, success criteria, and monthly checkpoints. No open-ended staff augmentation unless you ask for it.

  2. Owners on delivery

    A named senior engineer on architecture and incidents, plus specialists when you need depth, instead of a rotating bench.

  3. Coverage that fits your map

    On-call windows across MENA and EU so upgrades and incidents land in humane hours for your teams.

At a glance

  • <24h

    First response

  • 5+

    Senior engineers

  • 100%

    Code hand-back

  • MENA + EU

    On-call windows

What we ship

What we run in prod

Real systems for real teams. Senior staffing, scoped engagements, hand-back when you're ready.

Multi-region Kubernetes

GKE and EKS clusters with GitOps via Flux, blue-green deploys, SLO-backed runbooks, and pager coverage across MENA and EU windows.

Cloud cost ceilings, not surprises

Greenfield AWS and GCP architectures with cost guardrails in code. Lift-and-shift migrations with written budgets and a hand-back runbook your team can run.

Security from the architecture out

Threat modeling, IAM hardening, secrets hygiene, network segmentation. Secure defaults at the design stage, not bolt-on compliance theater.

Engagement shapes

Engagement shapes

We take engagements where we can put a senior on the pager. Five concrete shapes; we'll tell you which one fits.

  1. Platform migration

    Multi-region GKE or EKS migration with GitOps, blue-green deploys, and written runbooks. Typical engagement: a six-week sprint with a senior engineer embedded with your team.

  2. Cloud modernization

    AWS or GCP greenfield, or lift-and-shift from on-prem. Cost ceiling stated up front. Hand-back runbook included so your team owns the system after we leave.

  3. System design review

    Two-week architecture audit ending in a written report and a hand-back meeting. You walk away with a roadmap and a prioritized backlog — not a deck.

  4. Secure system design

    Threat modeling, IAM hardening, secrets hygiene, secure-by-default infrastructure. Standalone, or embedded inside a larger platform engagement.

  5. Incident response retainer

    Senior on the pager. MENA and EU on-call windows. Written SLA. Cancel any month — no multi-year lock-in, no surprise renewals.

Who answers the pager

Team

A compact team of senior engineers. The person you talk to is the person who ships the code.

Cloud + platform engineer

Designs and operates multi-region Kubernetes platforms. AWS, GCP, Flux, Terraform. Owns the on-call rotation and writes the runbooks.

System design + reliability engineer

Architecture audits, SLO definition, incident response. Pre- and post-mortem discipline. Production-system survivor; can argue against a fashionable architecture and back it up.

Engineer + business lead

Bridges technical delivery and engagement scope. Writes the contract, runs the milestones, answers the procurement questions in plain English.

Four phases

From intake to operate

  1. Discover

    One-hour call. We listen. You leave with a one-page assessment, free.

  2. Design

    Written scope, architecture sketch, success criteria. Both sides sign before we touch keys.

  3. Deliver

    Sprints with transparent weekly updates. Code lives in your repo from day one. Hand-back runbook starts from day one too.

  4. Operate

    Optional retainer for SLO ownership and on-call. Cancel any month. Your team takes over when ready, with code and runbook in hand.

Common questions

Frequently asked questions

Who do you work with?

Series A through D startups and growth-stage teams in MENA and globally. We only take engagements where we can put a senior on the on-call rotation.

Cloud only, or on-prem too?

Both. We design and operate on AWS, GCP, and Cloudflare; we also modernize on-prem workloads and bridge hybrid topologies. The choice is yours; we'll tell you the trade-offs in writing.

Strategy, implementation, or both?

Both. We write the architecture and we ship the code. No deck-only engagements; the contract states what runs in prod on the last day.

How do you handle security?

Threat modeling at the architecture stage, IAM hardening at the infrastructure stage, secrets hygiene at the operations stage. Secure-by-default, not retrofitted compliance.

What markets do you serve?

Syria and the Arab region as our home market, plus global clients delivered remotely. We work in English and Arabic; our team is in Damascus, our delivery is wherever your systems live.

Talk to us

Start a conversation

Tell us your platform and the problem. We will reply with a scoped proposal within 24 hours — or tell you we can't take it on.

First response within 24 hours

Email
hello@shadasoft.com
Office
Damascus, Syria
WhatsApp
Chat on WhatsApp