Network automation fitment
Match a client's requirements — cloud, on-prem or hybrid — to a fitting automation approach and tool stack.
Client intake questionnaire
Capture the client's requirements. Answer the questions or paste notes — we'll pre-fill the recommender for you.
Keywords like “air-gapped”, “multi-vendor”, “500 devices” or “GitOps” are detected automatically.
Where will automation run?
How big is the fleet?
How many vendors?
Compliance needs?
Team experience?
Existing CI/CD?
Saved submissions
Loading…
Deployment models
Cloud
Automation control plane runs in managed cloud runners.
Elastic compute
Managed secrets & SSO
Easy CI/CD integration
Watch outs: Egress to devices needed, Data residency concerns.
Best fit: Greenfield, SaaS-first orgs and distributed teams.
On-prem
Runners hosted inside your own management network.
Full data control
Low device latency
Works air-gapped
Watch outs: You own scaling & patching, More ops overhead.
Best fit: Regulated, latency-sensitive or air-gapped environments.
Hybrid
Central inventory in cloud; execution split across zones.
Best of both
Phased migration
Zone-local runners
Watch outs: More moving parts, Identity must federate.
Best fit: Enterprises modernising a brownfield estate.
What drives the fit
Scale & multi-vendor
Device count and vendor mix drive whether you need parallel orchestration (Nornir) and a vendor-neutral layer (NAPALM) vs. simple per-device scripts (Netmiko).
Security & compliance
RBAC, secret rotation, audit trails and air-gap constraints decide where runners live and how credentials and packages are sourced.
Team skills & CI/CD
Team maturity and existing pipelines determine whether you start declarative (Ansible) or go straight to a GitOps test-and-deploy workflow.
Fitment recommender
Set the client's requirements to get a tailored stack.
Deployment model
Fleet size
Vendor mix
Security posture
Team maturity
CI/CD pipeline
Recommended stack
Why this fits
- Multi-vendor estate → NAPALM normalises facts and config across platforms.
- Medium fleet → Nornir runs tasks in parallel across a structured inventory.
- Scale/multi-vendor → a source of truth (NetBox) keeps intent consistent.
- Hybrid → centralise inventory, but split runners between cloud and on-prem zones.
Learn the tools
Ready to put this stack to work?
Turn your fitment into action — generate production-ready automation, explore ready-made templates, or follow a guided learning path for the recommended tools.