Internal Developer Platform

A platform run as a product: a service catalogue with owners, golden paths for new services, self-service environments and guardrails, and the adoption routines that let product teams ship without filing tickets.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for Internal Developer Platform, and click Install. It goes into your own files, and works offline from then on.

What it installs.

1

Pillar

1

Area

50

Projects

204

Starter tasks

⚙️ Software Engineering

Internal Developer Platform

Building self-service paved roads for creating, deploying and operating services, so product teams ship safely without needing platform experts.

  1. Platform team charter and named customers
  2. Map of every path to production today
  3. Service catalogue with an owner for every service
  4. Ownership metadata file in every repository
  5. First golden path for a new backend service
  6. Developer portal build, adopt or buy decision
  7. Responsibility split between platform and product teams
  8. Baseline of time to first production deploy
  9. Paved road principles and the off-road policy
  10. Weekly platform intake and request triage
  11. Platform office hours for product teams
  12. Monthly service catalogue accuracy sweep
  13. Golden path template upkeep and drift updates
  14. Platform adoption and satisfaction numbers
  15. Quarterly roadmap review with customer teams
  16. Service level objectives for the platform itself
  17. Service maturity scorecards in the portal
  18. Monthly internal platform changelog
  19. Deprecation and sunset process for platform features
  20. Product management basics for platform teams
  21. Cognitive load and team interaction modes study
  22. Writing service templates with a scaffolding engine
  23. Policy as code for platform guardrails
  24. Platform API built on custom resources
  25. Docs as code for platform documentation
  26. User interviews with product engineers
  27. Self-service ephemeral preview environments
  28. Self-service databases and queues through the portal
  29. Self-service DNS names, certificates and routes
  30. Self-service secrets with short-lived credentials
  31. Default telemetry built into the golden path
  32. Cost per service shown in the portal
  33. One deployment spec per service
  34. Removing ticket handoffs from the path to production
  35. Second golden path for workers and scheduled jobs
  36. Portal launch to three pilot teams
  37. Golden path migration week for existing services
  38. Internal platform demo day
  39. Annual platform strategy review
  40. Retiring the legacy deployment scripts
  41. First platform engineer at a scaling startup
  42. Enterprise platform across business units
  43. Compliance evidence from the paved road
  44. Merging two platforms after an acquisition
  45. Moving an existing service onto the golden path
  46. Inner source contributions to the platform
  47. Multi-tenant clusters with team isolation
  48. Fleet-wide automated changes across repositories
  49. Supply chain provenance in the golden path
  50. Platform return on investment for leadership

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Platform team charter and named customers

This is a team plan, best installed into a shared workspace so everyone with a role in it can see and own their tasks. A platform team without a charter becomes the place every unowned infrastructure job lands, and within a year it is a ticket queue rather than a product.

First tasks

  • List every team that deploys software and the person who leads each one
  • Draft the problems the platform will solve first and the ones it will not
  • Pick three outcomes with a number attached, such as days to first deploy
  • Review the draft with two product engineering leads and the sponsor
  • Publish the charter and set a review date six months out

Map of every path to production today

Before building a paved road you need to know how many dirt tracks already exist: hand-rolled pipelines, a deploy script on one laptop, a shared cluster nobody admits to running. Mapping how each team gets a change from merge to production shows where the duplication, waiting and risk really sit, and usually reveals that three or four patterns cover most teams.

First tasks

  • Book a 30-minute walkthrough with one engineer from each delivery team
  • Record each step from merge to production and who has to approve it
  • Mark every step that needs a ticket to another team
  • Group the routes into patterns and count teams on each
  • Present the two patterns to pave first at the next engineering leads meeting

Service catalogue with an owner for every service

When an alert fires at night or a vulnerable library turns up in forty repositories, the first question is who owns this, and in most organisations nobody can answer quickly. A catalogue listing every running service with its owning team, repository, runtime and on-call route is the backbone the rest of the platform hangs from.

First tasks

  • Export the list of running workloads from each cluster and cloud account
  • Match each workload to a repository and a likely owning team
  • Send each team lead their list to confirm or reject
  • Escalate the orphaned services to engineering leadership with a decision date

Make it yours.

Install Internal Developer Platform, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.