What we cover
Architecture engagements are wide on purpose. The scope depends on what your platform actually needs — most engagements pick four to six of the following domains. The Discovery Sprint narrows it down.
- Cloud landing zone. Multi-account / multi-subscription structure, OU layout, baseline guardrails, cross-account networking, IAM blueprint, secret management, tagging and FinOps allocation.
- Multi-region & multi-cloud. Active-active vs active-passive, replication topology, failover sequencing, network topology, latency budgeting. Honest opinions about when multi-cloud is wrong (it usually is).
- Data platform & lakehouse. Warehouse / lakehouse selection, medallion vs vault vs star, semantic layer adoption, dbt project structure, orchestration design, BI repointing strategy.
- Security baseline. IAM least-privilege, encryption at rest and in transit, key rotation, audit logging, network isolation, secret management, SOC 2 / ISO 27001 / HIPAA / DPDP-ready posture.
- Disaster recovery & BCP. RPO / RTO budgets per workload, backup strategy, cross-region failover, runbook authoring, tabletop exercise design, restore-test automation.
- Observability. Logging, metrics, traces, SLOs, SLIs, error budgets, alerting policy, on-call rotation design. Tool-agnostic — we will tell you when Datadog is the right answer and when Prometheus + Grafana + Loki is.
- CI/CD & platform engineering. Build pipelines, IaC modules, environment promotion, golden paths, internal developer platform design.
- API & microservices. Domain boundaries, sync vs async, event-driven patterns, mesh vs ingress, contract testing, API gateway selection.
What you receive
- Written architecture document (60 – 120 pages) covering the chosen domains, with rejected alternatives and reasoning.
- IaC scaffold — Terraform organized by environment, modular, not pseudocode. Your team extends it on day one.
- Security baseline with explicit gap remediation steps per relevant framework (SOC 2 CC, ISO 27001 Annex A, DPDP).
- 12-month roadmap with sequenced milestones, headcount estimate, and budget bands per phase.
- Vendor-neutral build estimate — what it will cost with your team, with us, or with a Big SI.
When to engage us
- You are about to commit seven figures in platform spend and want a second opinion before signing.
- Your current platform was built three years ago by people who have since left, and the team is afraid to touch it.
- You need a credible architecture artifact to present to leadership, a board, or an auditor.
- You are about to migrate or merge platforms (post-M&A) and need the target state designed before you start moving.
How we engage
Starts with the Discovery Sprint (₹2 – 3 L / $3 – 5k, 10 days) — we scope which architecture domains are load-bearing for you and quote the full engagement. Architecture Engagement itself runs 3 to 8 weeks depending on scope, fixed fee, two engineers, three working sessions with your team.
If you proceed to a build, migration, or platform-management engagement with us within 60 days, the 5% Combo discount applies on that follow-on SOW.
FAQ
Can you architect for a specific cloud only?
Yes. Single-cloud designs (AWS, GCP, Azure) are the common case. Multi-cloud designs are rarer and usually wrong — we will tell you if your case is the exception.
Do you cover compliance?
Security baseline covers SOC 2, ISO 27001, HIPAA-ready, and India DPDP-ready postures. We do not run the audits themselves — that is your auditor's role.
What if my team disagrees with the architecture?
That is what the three working sessions are for. The final architecture is a synthesis, not a delivery. If we genuinely disagree on a load-bearing decision, the document records both positions with reasoning.