Skip to content
§
§ · hiring guide

How to Hire a Bare Metal Provisioning Platform Development Company

Ask what happens when provisioning fails at step six of nine. If the answer is a retry, ask what makes step three safe to run twice. Idempotency is the whole design.

Custom Software Development code editor and API illustration for Bare Metal Hosting Provisioning Platform.
The short answer

Ask what happens when provisioning fails at step six of nine. If the answer is a retry, ask what makes step three safe to run twice. Idempotency is the whole design. Expect $90,000 to $180,000 for discovery based inventory, a provisioning state machine covering switch and image work, address management and the reclaim loop.

A failing data centre makes noise. A failing provisioning platform makes none at all. It quietly leaves eleven machines powered, racked, holding addresses and drawing power with no customer and no invoice against them, and nobody notices because there is no alarm for revenue that was never billed. That silence is the reason this software is hard to evaluate: the worst outcome of a bad build is not an outage, it is a cost line that grows without a single error message.

Buying here is complicated by the fact that good open components already exist and none of them is the product. Boot and imaging engines are solved, and a firm that offers to write you a new one has misread the problem. What nobody sells is the layer above: catalog, order lifecycle, tenancy, address management, reclaim policy and billing, which together encode how your business turns metal into revenue. That layer is where the money and the risk sit, and it is exactly the part a portfolio of infrastructure work does not prove anyone can build.

What a provisioning platform firm actually builds

The customer portal is the visible fraction. Underneath it a machine needs an identity that exists before anyone is allocated to it: chassis serial, exact hardware configuration, interface addresses, management controller address and credentials, and the switch and port each interface actually landed on. That comes from discovery rather than data entry, because hand assembled inventory decays and a correct configuration applied to the wrong port is the most common provisioning failure there is. Above that sits a state machine with idempotent steps, explicit retries and a per machine timeline, since a run touches the switch, the management controller, a boot service, an image store, address records, name resolution and billing, and any of those can half succeed. Then a network abstraction that speaks to every switch platform in your halls and reads the configuration back after writing it. Then reclaim, which has more steps than provisioning and no customer waiting: sanitisation, controller reset, credential rotation, firmware baseline, address return and validation before the machine is sellable again.

What it costs in 2026

ScopeCost bandTimeline
Inventory truth and automated reclaim only, on the existing manual workflow$35,000 to $70,0006 to 10 weeks
First release: discovery based inventory, provisioning state machine with switch and image automation, address management, reclaim loop$90,000 to $180,00014 to 20 weeks
Full self service platform: customer interface, private networking and routing sessions, hardware validation, console access, billing integration$200,000 to $500,0006 to 12 months
Maintenance plus drivers for new hardware and switch platforms15 to 20 percent of build per yearRetainer plus per platform

Two costs are almost always absent from the quote. The first is enlisting the estate you already have. Discovery is straightforward for a machine you rack after the platform exists. For several hundred servers already in production, someone has to re-walk the halls, reboot machines into a discovery image during maintenance windows, reconcile what comes back against your spreadsheet, and resolve the ones that disagree. That is weeks of coordinated work with your operations team and it is not software effort.

The second is hardware variation. Management controller behaviour differs between vendors and, more awkwardly, between firmware generations of the same vendor, so a single client library does not survive contact with a mixed fleet. Older machines fall back to legacy management interfaces and vendor tooling. Every additional switch vendor adds a driver plus its own read back verification path. Ask each candidate to price by hardware family and switch platform rather than by server count, because server count is not what makes this expensive.

Signals of a strong partner

  • They answer failure questions with state, not retries. Every step safe to run twice, every failure leaving a nameable state the system can resume from.
  • They propose building on an existing boot and imaging engine. Rewriting that is a bad use of your budget and a signal about judgement.
  • They name controllers and switch platforms they have driven. By vendor and by generation, including which ones needed legacy fallbacks.
  • They verify configuration by reading it back. Assuming a write succeeded is how a machine sits on the wrong isolation boundary until traffic reveals it.
  • They treat reclaim as a first class deliverable. It is usually the fastest payback in the whole build, because the machines are already bought and already consuming power.
  • They ask about your sanitisation obligations. Contract terms and customer compliance regimes decide the level, and encryption with per tenant keys changes the economics of the wipe.
  • They want the internal lifecycle stable before any public interface. Exposing a workflow that still needs occasional manual repair produces support tickets faster than revenue.

Red flags

  • An offer to write a new imaging engine. The problem is solved, and the budget belongs in the layer above it.
  • A single management controller library for a mixed fleet. It will work in the lab and fail on your oldest two racks.
  • Reclaim described as a later phase. It is where your idle inventory is trapped, and deferring it defers the payback.
  • Tenancy isolation explained only in software terms. On shared physical infrastructure isolation is enforced in the switching layer, and a firm that does not say so has not built multi tenant hosting.
  • Any hesitation about repository and infrastructure account ownership. This platform encodes how your operations work, which makes the dependency structural rather than commercial.

Questions for the first call

  1. Provisioning fails at step six of nine. What state is the machine in, and how do you resume?
  2. What makes each earlier step safe to run a second time?
  3. Which management controllers and firmware generations have you driven, and where did you need fallbacks?
  4. Which switch platforms have you configured, and how do you verify the configuration took effect?
  5. How would you enlist several hundred machines that are already racked and in production?
  6. Walk me through reclaim step by step, including credential rotation and validation.
  7. How would you prove tenancy isolation to a customer's security reviewer?
  8. What is your sanitisation design, and how does encryption at rest change it?
  9. What has to be true internally before you would expose a customer facing interface?

A simple way to decide

Before you shortlist, gather two numbers this week: how many machines are currently powered but unallocated, and the median hours between order and credentials over the last quarter. Those are your business case, and they also tell you which candidate is listening. Then buy a paid discovery phase from your two strongest firms with identical deliverables: a hardware and switch inventory with per family estimates, a provisioning state model with named failure states, a reclaim design including sanitisation policy, an estate enlistment plan with maintenance windows, a phased scope with a fixed price for the first release, and a written specification that is yours to take elsewhere.

Digital Heroes works PRD first for exactly this kind of system, hands the client the repository and infrastructure accounts from the first commit, and contracts through an India LLP, a US LLC or a UK LTD so intellectual property assigns under your own law. Across 2,000 plus projects our record is verifiable through D-U-N-S, Clutch and Trustpilot.

Book a 30-minute call with Digital Heroes and get a written plan and a fixed quote within 48 hours.

Research & sources

The evidence behind this guide

Independent findings on why this investment pays off. Every link goes to the primary source.

  1. 48% of private companies cite integration with legacy systems or technical debt as a top obstacle to realizing the full value of their digital and AI investments (behind data quality/availability at 72% and gaps in AI fluency or technology talent/leadership at 53%). Source: Deloitte (2026) →
  2. Almost half of all the activities people are paid almost $16 trillion in wages to do in the global economy have the potential to be automated by adapting currently demonstrated technologies. Source: McKinsey Global Institute (2017) →
  3. The average number of formal learning hours used per employee fell to 13.7 in 2024, down from 17.4 in 2023, a decline the report attributes partly to a shift toward informal and on-the-job learning not captured in the formal-hours metric. Source: Association for Talent Development (ATD) (2025) →
  4. In Gartner's 2025 AI in Finance Survey of 183 CFOs and senior finance leaders (fielded May-June 2025), 59% reported using AI in their finance function, with accounts payable process automation adopted by 37% of respondents (the second-highest single use case, behind knowledge management at 49%). Source: Gartner (2025) →
FAQ

Frequently asked questions

How much does it cost to hire a bare metal provisioning platform developer?

A first release with discovery based inventory, a provisioning state machine covering switch configuration and imaging, address management and automated reclaim runs $90,000 to $180,000 over 14 to 20 weeks. A full self service platform with a customer interface, private networking, hardware validation and billing integration runs $200,000 to $500,000 across 6 to 12 months. Hardware and switch vendor diversity is the biggest single driver.

Should the developer build on an existing provisioning engine?

Yes, and be wary of anyone who offers to write a new one. Boot and imaging engines are solved by mature open projects and rebuilding them spends your budget in the wrong place. The value sits in the layer above: catalog, order lifecycle, tenancy, address management, reclaim policy and billing, which encode your business model and which no product will supply for you.

Why does automating reclaim matter more than automating provisioning?

Because provisioning has a customer waiting and reclaim does not, so reclaim tickets always lose to work with a deadline. Machines sit powered, racked and holding addresses after billing stops, which is cost with no revenue against it. Automating that loop is usually the fastest payback in the whole build, since the hardware is already bought and already consuming power in your halls.

How long does the build take before we can use it?

A first release ships in 14 to 20 weeks and should be genuinely usable rather than a prototype. The pacing item is hardware diversity, because management controller behaviour differs by vendor and firmware generation and older machines need legacy fallbacks. Add time for enlisting servers already in production, which means maintenance windows and coordinated work with your operations team rather than developer effort.

What should the contract say about ownership?

That you own the repository, the infrastructure accounts and the unrestricted right to hire another firm to continue, agreed before kickoff. At Digital Heroes the client owns the code from the first commit. This platform encodes how your data centre operations actually work, so a supplier dependency here is a dependency on your ability to turn inventory into revenue.

Should I ask for a fixed price or pay the agency hourly?

Fixed price for the first version, hourly or retainer for what comes after launch. A fixed-scope, fixed-price V1 puts the estimation risk on the agency, which is exactly where you want it while trust is unproven; hourly billing on an unscoped greenfield build is a blank check. After launch, flip it, because maintenance and small features arrive unpredictably and fixed-pricing every ticket wastes everyone's time.

Is a solo freelancer enough for my project, or do I really need an agency?

A solo freelancer is a fine choice for a well-defined build under roughly $15,000 to $20,000 with a limited lifespan: an internal calculator, a scripted integration, a prototype. Above $50,000, or for any system your business will depend on for years, you are buying continuity as much as code: enforced code review, cover when someone is ill, and support that outlasts one person's career plans. Price the risk of a single point of failure, not just the hourly rate.

How many SaaS seats do we need before building custom becomes cheaper?

The crossover usually shows up between 20 and 50 seats on premium tiers. Salesforce Enterprise lists at $165 per user per month, so 40 users cost about $79,000 a year in subscriptions, which is real money against a custom system you would own outright. Run the comparison over three years: if subscription spend beats the build cost plus 15-20% annual maintenance, custom wins on price before you even count workflow fit.

Will custom software work with the tools we already use, like QuickBooks and Stripe?

Yes, and this is one of custom software's genuine advantages: QuickBooks, Stripe, Shopify, and most mainstream business tools publish documented APIs built for exactly this. Expect each standard integration to add one to two weeks of build time, and be suspicious of any quote that lists five integrations without asking what data flows in which direction. The hard cases are legacy systems with no API, which is a question to raise in discovery, not in week nine.

Is it cheaper to customize Salesforce than to build a custom CRM from scratch?

If you use less than a third of what Salesforce does, a custom CRM is often cheaper by year three. Salesforce Enterprise lists at $165 per user per month, so 25 seats cost about $49,500 a year before admin and consultant fees, while a focused custom CRM runs $60,000 to $100,000 once plus 15 to 20% a year in maintenance. If you genuinely need Salesforce's ecosystem, reporting, and app marketplace, customizing it beats rebuilding it; the mistake is paying enterprise prices to use it as a glorified contact list.

How do I make sure custom software is secure and compliant with rules like HIPAA?

Start with the baseline every business system should have: encryption in transit and at rest, role-based access control, and audit logs. If HIPAA applies, the hosting provider must sign a Business Associate Agreement, which AWS, Azure, and Google Cloud all offer, and access controls have to be designed in from day one, not bolted on. SOC 2 certifies a company's operating practices, not a codebase, so ask vendors what they have shipped in your regulated domain rather than which logos are on their website.

What happens if I stop paying for maintenance after launch?

Nothing breaks on day one, which is what makes it dangerous. Within 6 to 18 months, unpatched dependencies accumulate known vulnerabilities, an integrated API like Stripe ships a breaking change, and the first fix requires a developer to relearn a stale codebase at full price. Budget 15 to 20% of the build cost per year for upkeep; it is the difference between a $500 patch and a $15,000 emergency.

What happens to my software if the agency shuts down or we stop working together?

Nothing dramatic, if the engagement was set up correctly: the code sits in your repository, hosting runs on your cloud account, and a handover document explains how to deploy and operate the system. Any competent replacement team can then take over in days rather than months. If the agency controls the repo, the servers, or the domain, fix that now, because renegotiating access during a dispute is the most expensive place to discover the problem.

Should I hire a freelancer or an agency for my software project?

A skilled freelancer is the right call for a single-discipline scope under roughly $15,000, like a website, a plugin, or one integration. Above that, projects need design, backend, testing, and project management at once, and a solo builder becomes the single point of failure: if they get sick or take a bigger client, your project simply stops. Agencies bill 20-40% more per hour but carry continuity, code review, and someone to escalate to, which is what you are actually buying.

How many people should be working on my software project?

Three to five for a typical focused build: a project lead, one or two engineers, a designer, and part-time QA, which is the standard shape across 2,000+ Digital Heroes projects. Larger platforms justify 6 to 10, but a ten-person team on a small first version usually signals bill padding rather than horsepower. What predicts success is whether a senior engineer is writing your code daily, not the headcount on the proposal.

How much should a small business budget for its first custom app or website?

For a focused first build, most small businesses land between $8,000 and $60,000: roughly $8,000 to $45,000 for a custom website and $25,000 to $60,000 for an internal tool or simple web app, based on Digital Heroes delivery across 2,000+ projects. Customer-facing products with payments, logins, or a mobile app start around $40,000. Quotes far below these bands usually mean a template with your logo on it, not software shaped around your workflow.

Who can build a custom software system?

Digital Heroes builds custom software systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, with an assigned senior team rather than an account manager.

Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.

What makes Digital Heroes different from other software companies?

Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.

Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.

How can I check Digital Heroes is legitimate before getting in touch?

Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.

Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.

Keep reading

Published · Last updated .

Online now

Hi there. How can we help you today?

Reply