Hi there,
It’s 2024 now, and that means it’s time to stop wasting time and start platform engineering properly. Every single day I’m hearing things like this:
- We’re currently planning capabilities and design to build our Internal Developer Platform next year.
- We’re in the research phase.
- We are setting up a working group.
Are you fucking kidding me? Do you think you can plan how to build an iPhone if you yourself have never used any phone? Do you think you can ask users what they want and the answers will make sense?
I can GUARANTEE that you will fail. And not even fast. You will fail the slow death of year long initiatives, committee meetings, missing adoption and frustration.
If you're serious about platform engineering I want you to have your Minimum Viable Platform in 14 days with the first app running on it by February. I can hear you grinning. Absurd! No it’s not. I’ve done it literally dozens of times. You’re just telling yourself it’s not possible to find an excuse not to act.
You have to feel an Internal Developer Platform. Your users have to feel it. Then learn, then iterate. Start small, nimble. Then ask users, then innovate.
Here’s how I guarantee you you’ll pull it off in 14 days:
- Use reference architectures to start: Here are the docs.
- Find your pioneer team.
- Integrate the first app.
And here’s what we’ve changed at Humanitec to support this motion:
- New pricing tier for teams up to 25 users - for only $999/month
- Includes Orchestrator, Score & the Portal (or Backstage) + all integrations you need.
- New professional services guaranteeing your first MVP in 14 days.
We’re running the most complex infrastructures for some of the largest enterprises in the world. Nothing about you is special. And should you not like it and really think you can self-roll this - do it with the experience you’ve gathered with us.
It’s time to act and to stop dreaming and tinkering. 14 days - just reading this you lost 250 seconds already.
Kaspar
