Design review before you build
A second pair of eyes on the topology, addressing, segmentation and failure domains while the design is still cheap to change, with the reasoning written down.
Our engineers on your project, until it lands
Design review, implementation, automation and root cause analysis, delivered by the engineers who run production networks and teach the labs. Your team keeps ownership.
Describe your project
- Section
- For US organizations
- Trained
- 3,000+
What is project support?
Project support places Tungabadra Networks engineers alongside your team for the length of one specific project, rather than delivering a document and leaving. It suits work that is already underway, work whose scope will move as you learn more, and work where your team has the context but not the capacity. The same engineers who run production enterprise networks do this work, so the depth is current rather than remembered.
Where it helps
Six places a project stalls
Each of these is a project with an end, not an open-ended retainer.
Implementation and rollout
Staged builds, configuration standards, change windows and cutover support for a new site, a refresh or a migration, including the rollback plan.
Automation build
Turning a repetitive change into a tested, version-controlled tool: Python and Netmiko against your fleet, Ansible playbooks, and validation that runs before anything reaches a device.
Security and segmentation work
Firewall policy review, rule base cleanup and segmentation design across Palo Alto and multi-vendor estates, with each change justified rather than assumed.
Monitoring and visibility
Alert coverage that catches what matters and stays quiet otherwise, plus the dashboards and thresholds your operations team will actually use.
Root cause on a recurring fault
Packet-level investigation of the intermittent problem that keeps reopening, ending in a written root cause analysis and the change that closes it.
How it works
From first call to documented handover
A written proposal before any commitment, and a handover your team can maintain.
Scoping call
You describe the project, where it stands and what is blocking it. We say plainly whether we are the right fit.
Written proposal
Scope, the engineers assigned, the working pattern, expected duration and a fixed price in US dollars.
Work alongside your team
Our engineers join your calls and your change process. Your team keeps ownership and makes the decisions.
Documented handover
Configurations, diagrams, runbooks and any tooling built, handed over so your team can maintain it without us.
What you get
What leaves with you at the end
- Named engineers, not a rotating pool
- Working inside your change process rather than around it
- Configurations and topology diagrams kept current as the work goes
- Runbooks for anything your team will operate afterwards
- Any tooling built, in your version control, with its history intact
- A written close-out covering what was done and what remains
What this is not
Project support is deliberately bounded, and it is worth being clear about the shape so the proposal matches what you need:
- Not an open-ended retainer
- Not managed services or a staffed NOC
- Not a handover of ownership to us
If ongoing operations are what you are after, technology services covers managed network services and NOC support instead.
Questions
Project support FAQ
What is project support at Tungabadra Networks?
Project support places our engineers alongside yours for the duration of a specific piece of work, rather than handing over a finished deliverable and leaving. The scope is a project with an end: a design review, a site rollout, an automation build or a recurring fault nobody has closed out.
How is this different from technology services?
Technology services are scoped engagements with a defined deliverable, such as an architecture review or a security readiness assessment. Project support is people working with your team on your project, on your schedule, and it is the right shape when the work is already underway or the scope will move as you learn more.
Do you take over the project?
No. Your team keeps ownership and makes the decisions. Our engineers add capacity and vendor depth where you need it, and everything they build is documented so it stays maintainable after they leave.
Which vendors and platforms do you cover?
Cisco, Juniper, Palo Alto, Aruba and Arista on the network side, AWS on the cloud side, and Python, Ansible and CI/CD tooling for automation. These are the same platforms the engineering division runs in production and teaches in the labs.
Can you work remotely?
Yes. Most project support is delivered remotely, with on-site attendance arranged where a cutover or a physical build needs someone in the room.
How is it priced?
Engagements are quoted per project in US dollars, based on scope, duration and how much on-site time is needed. Send the project details and you will receive a written proposal before any commitment.
Describe your project
Tell us what is blocking it
Include what the project is, where it currently stands, the platforms involved and what done looks like. You will receive a written proposal with scope, working pattern and a fixed US dollar price.
- No cost and no obligation for the scoping call or proposal
- Response within one business day
- We will say if the work does not need us
Need the team trained as well?
Corporate training runs the same engineers as instructors, scoped to the stack your team already works on.