Hey {{first name | there}},
Yes, I am taking over Jubril today. I promise, just today alone 😂
Leadership saw a Backstage demo. Now they want a portal. The platform team knows they're not ready. No one is saying it out loud.
In this issue:
⚠️ Why your portal will expose every broken thing about your platform, not hide it
📋 A 5-question self-check to know if you're actually ready
📡 3 signal picks from the platform engineering ecosystem this week
PARTNER
Most platform teams build the portal before the platform is ready for it.
The self-service interface looks clean. The chaos underneath it doesn't go away, it just becomes more visible to more people.
Octopus Deploy's Platform Hub lets you surface what already works: standardized pipelines, consistent deployments, and golden paths developers actually trust.
Build the roads first. Then give your team the GPS.
PRODUCTION NOTES
The portal trap
There's a conversation happening in every mid-sized engineering org right now. Leadership attended a conference, saw a beautiful Backstage demo, and came back energized. Now "launch developer portal in Q2" is on the roadmap.
The platform team nods. And quietly knows they're not ready.
Matthew Allford from Octopus Deploy put it well: a portal is the GPS, the platform is the road. If the roads aren't built, the GPS doesn't navigate you somewhere useful. It navigates you into a field.
The portal doesn't fix an inconsistent platform. It just makes every inconsistency visible to more people, faster.
Why everyone wants the portal first
Two core reasons:
↳ They demo well.
↳ They're tangible.
Also, "Launch developer portal in Q2" shows up well in a board update in a way that "reduce process drift across 14 teams" never will, even though the second one is the thing that actually moves the needle.
This is a measurement problem disguised as a tooling problem. Teams ship what executives can see.
The result is portals built on platforms that aren't ready to be surfaced, and within six months, the portal has exposed every inconsistency to the entire engineering organisation.
The 5-question platform readiness check
Before your next conversation about portals, run through these. Be honest.
☐ Can a new engineer deploy to production on day one without someone walking them through it?
☐ Do two teams deploying the same service type run the same process meaningfully?
☐ When you change the delivery process, does that change get tested before production?
☐ Are governance and compliance rules enforced in code or in PDFs?
☐ If you built a portal tomorrow, what would you actually put in it?
Score informally.
If three or more of those made you cringe, the portal is probably the wrong next investment. Fix the foundations first.
What solid foundations actually look like
Most DIY platforms have one or two of these. Almost none have all four working together:
Reusable delivery templates: a new team can ship on day one without reinventing the pipeline
Policy as code: governance is enforced automatically, not audited after the fact
Centralised governance with team autonomy: the platform team sets the guardrails; teams move freely within them
Auditable versioned changes: every change to the delivery process is tracked, tested, and reversible
A portal built on top of these four foundations is powerful. A portal built without them is a liability.
As Paul Stovell, Founder & CEO at Octopus Deploy, put it: build-it-yourself isn't a platform strategy. It's a dead end.
Where this leaves you
Portals are genuinely powerful — for organisations that have done the foundational work. The point isn't to avoid them. The point is to invest in the right thing at the right time.
The roads come first.
If you're dealing with this or have made the call to delay the portal in favour of foundations, I'd genuinely like to hear how that conversation went. Reply to this email.
PARTNER
Most platform teams build the portal before the platform is ready for it.
The self-service interface looks clean. The chaos underneath it doesn't go away, it just becomes more visible to more people.
Octopus Deploy's Platform Hub lets you surface what already works: standardized pipelines, consistent deployments, and golden paths developers actually trust.
Build the roads first. Then give your team the GPS.
Until Next Time
The portal conversation isn't going away. Leadership will keep bringing it up. The job this week is to answer it with a better question: are our roads ready?
Run the five-question check with your team. If you're not passing three or more, that's the roadmap. Everything else is decoration.
If this was useful, forward it to one engineer who'd find it valuable. It's the best way to grow this community.
Divine Odazie
Your Favourite Platform Engineer 😃
