Service

New infrastructure provisioned consistently from a trusted source of truth, with far less engineer time

We build the path a new device takes from the box to service: it is racked, cabled and powered on, then fetches its image and its configuration on its own, and is validated before it carries traffic. The configuration comes from your source of truth, the one you run today or one we build with you.

Measured impact

What changes for your organization

  • Today

    Weeks to bring up a rack

    Every new device is configured by hand, one console session at a time, and a new rack waits for engineers to be free.

    With zero-touch provisioning

    Capacity in service sooner

    Devices configure themselves as they are powered on, so new racks and sites reach service sooner.

  • Today

    Senior engineers on console cables

    Skilled people spend their days on day-zero setup, or travel to sites to do it.

    With zero-touch provisioning

    Engineer time back

    The field job ends at racking, cabling and power, and engineers spend their time on design and operations.

  • Today

    Every device a little different

    Hand-typed configuration varies by who did it and when, and the differences surface later as faults.

    With zero-touch provisioning

    Consistent configuration

    Every device gets its configuration from the source of truth for its role and position, the same way every time.

  • Today

    Errors found after go-live

    A wrong uplink or a missing setting shows up once the device already carries traffic.

    With zero-touch provisioning

    Validated before service

    Each device is checked against its intended state before it enters service, so faults are caught on the bench.

  • Today

    Replacements from backups

    A failed device is rebuilt from an old configuration backup, if one exists and is still current.

    With zero-touch provisioning

    A replacement boots into its role

    A new unit takes the failed one’s place and fetches the configuration that role needs today.

What we deliver

  • Device onboarding

    The boot path for your hardware, DHCP and a boot file, ONIE, POAP or the vendor’s equivalent, set up for every platform in your estate.

  • Image and configuration from the source of truth

    The right software image and the configuration for each device’s role and position, generated from your source of truth at the moment it boots.

    Read the case study →
  • Validation before service

    Checks of cabling, software and configuration against the intended state, so a device enters service only when it passes.

  • Bring-up at scale

    Many devices brought up in parallel across racks and sites, from one request or as each unit is powered on.

    Read the case study →
  • A secured provisioning path

    The provisioning network, the boot servers and the images protected and verified, so only the intended software and configuration reach a device.

  • Integration with your tools

    Provisioning connected to your source of truth, IPAM, ticketing and monitoring, so a device is recorded, watched and handed over as it comes up.

How it runs

The scope scales with your hardware and your sites; the order of the work stays the same.

  1. Discovery

    How devices are brought up today, your hardware and source of truth, the target provisioning flow, and a plan that starts with one device role.

  2. Source of truth

    The data provisioning needs, read from the source of truth you run, or from one we build with you first.

  3. Boot path

    DHCP, boot servers, images and the onboarding mechanism for each platform, set up in a lab.

  4. Configuration and validation

    Configuration generated per role from the source of truth, and the checks a device passes before it enters service.

  5. Rollout

    The first rack or site in production, then the other roles, platforms and sites.

  6. Handover

    Your team runs and extends the provisioning, documented and owned in-house, with our support for as long as you want it.

It starts from your source of truth

Provisioning is only as good as the data it reads, so the first choice is where that data comes from.

  • The source of truth you run

    NetBox, Nautobot, an IPAM or an in-house database. We connect provisioning to it and add the data a device needs to boot into its role.

  • A source of truth we build

    Where the records are spread across spreadsheets, we build the record first, as its own project, and provisioning reads from it.

Proof

Zero-touch bring-up in a production data center fabric, and automated bring-up of test networks at scale.

Why CodiLime

  • Zero-touch in a production fabric

    For a global e-commerce marketplace we built SONiC ZTP bring-up, where every switch boots production-ready with the configuration for its role.

  • Sites brought up from the center

    For a retail enterprise, zero-touch provisioning brought a couple hundred sales points onto its SD-WAN, each one configured remotely from the center.

  • Vendor-neutral by design

    One configuration model with a renderer per hardware platform, so a new vendor in the fabric means a new renderer.

FAQ

Good to know

  • Do we need a source of truth first?

    Provisioning needs trusted data about each device and its role. If you run a source of truth today, we connect to it; if your records live in spreadsheets, we build one first as part of our Network Source of Truth service.

  • Which hardware does it work with?

    Most data center and campus platforms boot through DHCP with ONIE, POAP or the vendor’s own mechanism, and SONiC has its own ZTP. The discovery lists what your hardware supports and how each platform comes up.

  • What is left for the people on site?

    Racking, cabling and power. From there the device fetches its image and configuration, and the result of its checks reaches your team remotely.

  • Is a device that configures itself safe?

    The provisioning path is designed for it: a separate provisioning network, verified images and configuration served only to the devices expected. Validation then confirms each device matches its intended state before it carries traffic.

  • Who runs it afterwards?

    Your team, with the provisioning documented and owned in-house. We stay on for support, new platforms and new device roles for as long as you want us to.

Start with a provisioning assessment

Tell us how new devices come into service today. We map your hardware, your source of truth and the manual steps, design the target provisioning flow, and hand you a plan that starts with one device role.