A production-ready developer platform. Live in 14 working days.

Start the €2,500 Platform Readiness Assessment: enter your company, name and email, pay securely, activate your account, then complete a short setup in your workspace — about 10 minutes. PlatformBox reviews readiness and starts the Assessment; the 3–5 working days begin then. Talk to Roberto first if you have questions; a call is optional. The Assessment fee is credited toward Launch if you proceed within 90 days.

You can — and some teams should. PlatformBox is for teams that would otherwise spend months redirecting senior engineers into platform work. We deliver a working developer path to production in 14 working days using a proven reference architecture, then hand it to your team to own and operate. You get the result without the months of internal engineering, the unresolved architecture decisions, and the adoption delay.

No — this is built for teams that haven’t hired a dedicated platform engineer yet, not to replace one that exists. If you already have DevOps or SRE headcount, involve them in the Assessment: the platform they’d run day-to-day is exactly what’s being scoped, and their read on fit matters more than ours.

A working developer path to production: an AWS/EKS foundation, Terraform modules, CI/CD, one golden path proven to production, preview environments, baseline security, documentation, and a live handover. On day 14, a developer can create a service from the standard template, deploy it to a preview environment, pass automated security checks, and promote it to production.

No. PlatformBox integrates the tools you already use and makes them work together. It owns the golden path, not the infrastructure beneath it.

The public reference implementation is GitLab for both source and CI — it demonstrates the complete DevSecOps golden path in one place. GitHub (source hosting or Actions) is delivered as defined scope where that is the customer’s stack.

You do. Everything lives in your AWS account, your repositories, and your Terraform, under your governance. You keep the documentation, runbooks, and architecture. There is no proprietary runtime creating lock-in.

Temporary, scoped access to your AWS account and source repositories for the 14 working days. We agree the exact scope and permissions up front.

During the 14 working days, access is granted through AWS IAM Identity Center (SSO) — MFA-enforced, scoped to a permission set you create, and revocable by you at any time. There’s no root usage and no static access keys, and every action is recorded in CloudTrail. That access ends at handover; an ongoing PlatformBox Care engagement uses the same scoped-SSO model, not standing credentials. Once built, the platform doesn’t depend on us to keep running: CI reaches your Kubernetes cluster through a GitLab Runner inside your own VPC, on your own AWS account, authenticated via OIDC rather than a static key. Production has no public API endpoint — the only way in for anyone, us included, is through that in-VPC runner over AWS Systems Manager, never SSH.

You run the platform with your team. Launch includes handover and training, and PlatformBox Care is available for ongoing maintenance and evolution.

That's what the Platform Assessment is for. If your environment doesn't fit the 14-working-day scope, we'll tell you before you commit — and propose a scoped Enterprise engagement instead.

The Platform Assessment exists precisely to prevent this. We only commit to a fixed-price 14-working-day scope after mapping your current state. If the assessment shows the scope isn't realistic, we tell you before any implementation begins — and agree a realistic scope or a different package.

Yes. PlatformBox Care provides ongoing platform engineering — maintenance, upgrades, security updates, and new golden paths — for €2,000–€4,000/month. It's optional; the platform keeps running without it. Care does not include alerting or on-call incident response — no package pages anyone today; the observability baseline is dashboards and metrics, not paging.

Each package has a fixed scope. Launch covers one primary AWS environment and one golden path; Scale adds multiple golden paths and environments. We don't force every workload onto the same shape — the exact list of what's in and out for your stack is mapped during the Platform Assessment, before any fixed-price commitment, not discovered mid-engagement. None of what's excluded is a gap in the 14-day promise — it's the reason the 14 days is credible for what it does cover. Scale and Enterprise extend what's covered; the Assessment determines which parts you'd actually need.

No. PlatformBox doesn't require a rip-and-replace of your existing platform. The pattern is: Assessment determines fit, you select one workload to pilot, we deliver and validate it end to end, you accept it — then expand to more workloads and teams on the same foundation. You keep running everything else exactly as it runs today until you choose to bring it across.

Baseline security is part of every engagement: least-privilege IAM, encrypted storage and state, application secrets held in AWS Secrets Manager and delivered to pods by the External Secrets Operator over federated identity — scoped per environment, so one environment cannot read another’s — and automated security checks in the pipeline. Additional security controls are available in Scale and Enterprise.

No — we don’t hold any of those certifications today, and we won’t imply otherwise to close a deal. If your procurement process requires a certified vendor regardless of the technical access model, raise it before the Assessment, not after — we don’t have a report to produce on short notice. The structural difference worth weighing: the platform lands in your own AWS account and GitLab org from day one, we don’t operate a multi-tenant service on your behalf, and standing access ends at handover — a different risk shape than a typical SaaS vendor, though not a substitute for certification if your framework requires one.

Two distinct things, and we keep them apart. THE PROMISE: a golden path proven to production, plus the implementation approach behind it, delivered in 14 working days — subject to the agreed assessment and scope. THE REFERENCE IMPLEMENTATION: a production-shaped, cost-optimised, publicly inspectable build that proves the pattern end to end. Three services now run it; the third was created by the platform’s own generator and reached production on 27 August 2026, promoted from UAT’s approved image with no rebuild, reconciled by ArgoCD, and health-checked from inside the production cluster (ADR-019, ADR-020, ADR-023). What it does NOT mean: we do not claim enterprise-readiness, alerting or log aggregation — see what PlatformBox does not do.

An IDP product is a tool, not a finished platform. The product still needs to be implemented: integrated with your cloud and CI/CD, wired to your repositories, given golden paths, and governed. That is exactly the engineering work PlatformBox delivers. You can adopt an IDP product and have PlatformBox implement and configure it — or use our reference architecture without one.

PlatformBox owns the platform engineering: infrastructure, delivery pipelines, golden paths, security controls, and observability. You own your application logic, product requirements, and application-level operations. A few things sit between us and are handled jointly: security incidents that touch the platform layer, cloud-provider outages, and disaster recovery where it spans both. During a Care engagement the same split carries forward — PlatformBox keeps the platform current and secure, you keep running your applications on it, and the shared items stay shared. PlatformBox is a defined platform scope, not unlimited outsourced DevOps.

Launch includes onboarding up to two initial services to prove the golden path with real workloads — the reference implementation demonstrates three services with independent lifecycles. Additional application onboarding is a defined expansion, not per-service billing.

Platform expansion modules: additional golden paths, environments, teams, a developer portal, self-service databases, advanced security or observability, and Enterprise compliance. Each is a fixed-scope engagement agreed during the Platform Assessment.

PlatformBox is a new specialist practice. The delivery model was built and exercised against a public reference implementation before taking it into customer environments. We don't claim customer outcomes we haven't earned yet. What we do offer is inspectable technical evidence: a public reference implementation, published decision records, and proven end-to-end delivery — all independently verifiable before any engagement.