Skip to content

Lesson 5 of 6

Costs and risks to weigh up

Add a risks section by recognising the costs and trade-offs of building or buying a platform.

4 minPlatform Engineering

After this lesson, you will be able to list the main costs and risks of building or buying an internal developer platform, and explain how they affect a team's decision.

The price of a platform

A platform is not free, even if you build it with open source tools. You pay with money, time, and attention. Before you recommend a platform, you need to know what it will cost and what could go wrong.

Think of a platform as a product inside your company. The team that builds it is a product team. They need to talk to users, design features, write code, test, and support the platform. That work takes people and time.

If you buy a platform from a vendor, you pay a subscription or licence fee. You also pay to set it up, move your existing tools and workflows onto it, and train your developers. These costs are easy to forget when you compare prices.

Building your own platform

Building a platform means you control everything. You choose the tools, the user interface, and how it fits your company. But control has a price.

First, you need a team. A small platform team might have two or three engineers. A larger one might have ten. These engineers are not building your product; they are building tools for other engineers. That is an ongoing cost, not a one-time project.

Second, building takes time. A simple platform might take a few months. A full platform with templates, pipelines, and environment management can take a year or more. During that time, your developers still do their work the old way, so you do not see the benefits yet.

Third, you must maintain what you build. Tools change. Your company's needs change. The platform team must keep the platform working, add features, and fix bugs. If the team moves on, the platform can become abandoned software that nobody understands.

Buying a platform

Buying a platform means you pay a vendor for a product that already exists. You can start using it quickly, and the vendor does the maintenance. But you give up some control.

First, you depend on the vendor. If the vendor raises prices, changes the product, or goes out of business, your platform is at risk. You may not be able to move your data and workflows to another vendor easily.

Second, a bought platform may not fit your company perfectly. You might need to change your processes to match the platform, rather than the other way around. Customising a bought platform can be expensive and may break when the vendor updates it.

Third, you still need people to run the platform inside your company. Someone must configure it, manage users, and help developers. That is a smaller team than building, but it is not zero.

Hidden costs and risks

Both building and buying have hidden costs. Here are some to watch for.

  • Integration: Your platform must work with your existing tools, such as your code repository, your CI system, and your cloud provider. Connecting these can take more time than expected.
  • Adoption: Developers will not use a platform that is slow, confusing, or gets in their way. If adoption is low, you pay for a platform that does not help.
  • Security: A platform has access to your code, your infrastructure, and your secrets. A mistake can expose your company. You need to invest in security from the start.
  • Lock-in: The more you build on a platform, the harder it is to leave. This is true for both home-built and bought platforms.

Weighing the costs

To decide, compare the total cost of ownership over three to five years. Total cost of ownership means all the costs: people, licences, infrastructure, training, and support.

For building, estimate the size of the platform team, their salaries, and the time to first release. For buying, get a quote from the vendor, add the cost of setup and training, and estimate the cost of the people who will run it.

Also think about risk. If your company has unusual needs or strict security rules, building might be safer. If you need something quickly and your needs are standard, buying might be better.

There is no one right answer. The best choice depends on your team's size, budget, and goals. In the next lesson, you will use what you have learned to write a recommendation.

Key takeaways

  • A platform costs money, time, and attention whether you build it or buy it.
  • Building gives you control but requires a dedicated team and ongoing maintenance.
  • Buying is faster to start but creates dependency on a vendor and may not fit your needs.
  • Hidden costs include integration, adoption, security, and lock-in.
  • Compare total cost of ownership over several years, including people and risk, before deciding.

Try it

Choose a small software team you know, or imagine one with five developers. List three tools they use daily, such as a code repository, a CI system, and a cloud provider. Write two short paragraphs: one estimating the cost of building a simple internal platform for this team over three years, and one estimating the cost of buying a platform from a vendor. Include people, setup, and ongoing costs in each estimate. Then write one sentence saying which option you would recommend and why. A good result names specific tools, gives realistic numbers for team size and time, and explains the trade-off between control and speed.

Official documentation

Ready to use this in a job?

Rolebound applies to matching roles for you.

Start now

Written with AI and checked automatically. Tools change, so a command may behave differently in the version you install. Spotted a mistake? Tell us.

    Cookies on Rolebound

    We use necessary cookies to sign you in and keep the site working — those cannot be turned off. We would also like to set analytics and advertising cookies so we can see which pages help people get interviews and which adverts brought them here. Nothing optional is set unless you say yes, and you can change your mind at any time from “Cookie settings” in the footer. Read our Privacy Policy.