The 14-Day Blueprint
See exactly what your team receives
A visual walkthrough of the platform that ships in 14 working days — from modular Terraform to production Kubernetes.
The 14-Day Blueprint
How the 14 working days work.
Assess → Build → Prove → Outcome — the four-stage engagement that delivers a working platform.
Phase 1
Assess
Map the current state, agree the target architecture, and lock the 14-working-day scope.
Phase 2
Build
Stand up the AWS/EKS foundation, networking, and baseline IAM.
Phase 3
Build
Standard pipelines, registries, and the commit-to-production workflow.
Phase 5
Build
The standard service template and repository bootstrap developers follow.
Phase 6
Build
Least-privilege access, encrypted storage and state, and automated checks in the pipeline.
Phase 7
Build
Prometheus + Grafana — metrics and dashboards, live-proven across both services (ADR-018).
Phase 8
Prove
End-to-end validation of the golden path against a real workload.
This is the standard PlatformBox delivery model. Individual environments may require scope adjustments identified during the Platform Assessment.
01 / The Timeline
Your 14-Day Journey
Two weeks, one fixed-price engagement — from foundation to a working path to production.
Week 1 — Foundation (Days 1–5)
Days 1–2
Architecture & foundation
Current-state review, target architecture, and the AWS/EKS foundation.
Days 3–5
Infrastructure & IAM
Terraform modules, networking, RBAC, secrets, and environments.
Week 2 — Delivery path (Days 6–10)
Days 6–7
CI/CD & environments
Standard pipelines, preview environments, DEV → QA → UAT promotion gates, GitOps reconciliation, and the production deployment workflow.
Days 8–10
Golden paths & preview
Service template, repository bootstrap, and preview environments.
Week 3 — Production readiness (Days 11–14)
Days 11–12
Security & observability
Security controls, live-proven application observability (Prometheus + Grafana), and cost controls.
Days 13–14
Validation & handover
End-to-end validation, documentation, training, and a phase-2 backlog.
02 / The Four Deliverables
What Your Team Receives
Click any card to view sample code, config, or interactive demos.
03 / The CI/CD Pipeline
From Commit to Production
Six automated stages — click any stage for details.
04 / Platform Capabilities
Proven now. Delivered later.
What the reference implementation proves today, and what ships as an optional Scale or Enterprise extension.
05 / Reference Results
What the reference platform actually measures.
These numbers come from exercising the PlatformBox reference implementation. Your engagement is built on the same process and tooling; the specific timelines depend on your environment complexity.
Before
3 weeks to ship a new service
After
1 click — under 5 minutes
Before
Every deployment needs DevOps help
After
A self-service golden path
Before
Idle staging environments burning cloud budget
After
Auto-destroy on merge — €0 waste
06 / Building it yourself
Building internally vs. the PlatformBox Blueprint.
The same outcome, two different timelines.
| Dimension | Building internally | PlatformBox Blueprint |
|---|---|---|
| Timeline | 6–12 months, often longer | 14 working days |
| Cost model | Open-ended hiring + tooling spend | Fixed price, €20,000 |
| Who builds it | A platform team you have to hire first | One engineer, 16 years in the stack |
| Scope risk | Discovered mid-build | Fixed before Build starts, via the Platform Assessment |
| Ownership | Yours from day one | Yours from day one — same repos, same AWS account |
07 / Before you start
What's in the 14 working days — and what isn't.
Fixed scope, stated up front. The Platform Assessment locks these in for your environment before Build starts.
In scope — PlatformBox Launch
- AWS/EKS foundation
- Terraform modules
- CI/CD (GitLab)
- One golden path proven to production
- Preview environments
- Production deployment workflow
- Up to 2 initial services onboarded
- Baseline security
- Observability (Prometheus + Grafana)
- Cost visibility (FinOps)
- Documentation & runbooks
- Handover & training
Out of scope for the 14 days
- A developer portal or web UI (Backstage-style catalog) — available as a Scale/Enterprise extension
- Self-service database provisioning — available as a Scale/Enterprise extension
- Multiple golden paths, multiple environments, or multi-team governance — that's PlatformBox Scale
- Multi-account AWS, multi-region, service mesh, or compliance scopes — that's PlatformBox Enterprise
- Application development, staff augmentation, or ad-hoc cloud troubleshooting
The proof surface
Each capability claim links to the evidence behind it.
The 19 evidence keys below are the delivery standard's proof contract — named in the standard, produced on a fixed working day, and each resolved to a public file in the reference implementation. Click any key to read the actual artifact, not a summary of it.
Hash-linked & verifiable
Every attestation is chained by hash to the one before it, in the control plane at /admin. A tampered record breaks the chain and is detectable, not silent.
Public-safe
Real customer evidence is tenant-scoped and never exposed. The files below come from the reference engagement only — no engagement ids, no proven_with data.
Customer Zero
PlatformBox is deliberately its own first customer. The proof you can read is our own reference implementation, built and verified in public.
Derived
Generated from tool output — a terraform plan, a CI log, a scan report. Anyone can re-run the command and see the same result.
Attested
Recorded in the audit chain — a human-signed fact about the engagement, linked by hash to what came before it.
Week 1 — Foundation
e-scope-statementattestedDOCUMENTConfirmed scope statement
The scope statement as acknowledged by the customer.
e-assessmentattestedDOCUMENTAssessment findings
What was found, and what it implies for scope. Customer-specific — attested inside the engagement, not published.
e-access-verifiedderivedCONFIGURATIONAccess verification output
Recorded output of the access verification runbook.
e-architectureattestedDOCUMENTArchitecture summary and diagram
The agreed architecture as presented at the review.
e-iac-planderivedIAC_PLANInfrastructure plan showing zero drift
Plan output against live infrastructure.
Proves: AWS foundation, Infrastructure as Code (Terraform), Networking
e-cluster-proofderivedDEPLOYMENTCluster reachable
Authenticated API call against the provisioned cluster.
Proves: AWS foundation, Kubernetes / EKS
Week 2 — Delivery
e-oidc-proofderivedCONFIGURATIONOIDC trust verification
Proof that CI assumed a role with no stored credential.
Proves: IAM & least privilege
e-scan-blockingderivedSECURITY_SCANSecurity scan blocking a build
A pipeline that failed on a deliberately introduced vulnerability.
Proves: Security scanning
e-pipeline-greenderivedCI_RUNFirst green pipeline
Pipeline URL and result.
Proves: Container registry, CI/CD
e-tiersderivedDEPLOYMENTTiers provisioned and reachable
Per-tier deployment record.
Proves: Preview environments
e-gate-blocksderivedCONFIGURATIONGated tier refused an unapproved promotion
Evidence that the gate is enforcing, not decorative.
Proves: Production promotion & controls
e-generated-servicederivedCI_RUNGenerated service pipeline
The pipeline for a service produced by the generator.
Proves: Golden Path (build -> production), Self-service (service creation)
e-promotion-digestderivedDEPLOYMENTIdentical digest across tiers
Digest recorded per tier, proving promotion without rebuild.
Proves: Golden Path (build -> production), GitOps / declarative deployment, Production promotion & controls
e-rollbackderivedROLLBACKRollback rehearsal
Rollback executed and the prior digest confirmed restored.
Proves: Golden Path (build -> production)
e-scrape-targetsderivedMONITORINGScrape targets up across all tiers
Target list with tier and cluster labels.
Proves: Metrics
Week 3 — Production & handover
e-costattestedCOSTCost breakdown
Per-tier cost with assumptions stated.
Proves: Cost control (FinOps)
e-reproductionderivedTEST_OUTPUTReproduction executed
Output of rebuilding from the written procedure.
e-runbooksattestedDOCUMENTOperational runbooks
The runbook set as delivered.
e-handover-packderivedDOCUMENTHandover pack
The generated pack as delivered.
Proves: Documentation & handover
Browse the full evidence tree in the reference implementation:docs/evidence Delivery standard v1.2.0 — 19 keys across 14 working days.