Add a node when the team grows, from the same console
A pilot starts on one server. A company grows into several. Adding a node is a form in the console, not a weekend project.
Start small
One server is enough for a pilot with a few developers. The console and a node can share the machine, and the first profiles are issued the same day. The installation grows from there without a rebuild: the server you started on becomes one node among several.
Adding a node
- Rent or pick a Linux server, wherever you want the traffic to leave from.
- Add it in the console.
- The console provisions the node the same way every time, and retries steps that fail.
- Assign devices to the new node.
The console provisions the node the same way every time, so there is no checklist to keep in a wiki. The steps are the same for the second node and for the tenth.
See the load before it hurts
The capacity view shows the load on each node, next to the live status of every node and device. When one node runs warm, you see it in the console and add another before developers notice.
Nodes where you need them
Nodes can stand in different places or with different providers. Each one is a server you own or rent, so the address the AI services see from each node is yours.
Devices are assigned to a node by the administrator. That keeps the picture simple: you know which developers use which node and which address they leave from, and the console shows the load on each.
Growing in steps
You do not need to plan the final size in advance. A sensible path looks like this.
- Pilot. One server, a handful of developers, the console and a node on the same machine.
- Team. A separate node for the developers, so the console is not sharing a machine with the traffic.
- Company. Several nodes, in the regions where your people work, each with its own address that you own.
At each step the console, the clients and the profiles stay the same. Only the number of nodes changes, and the work to add one is the same on the first day and on the last.
What does not change as you grow
Developers keep the same client and the same profile link. The administrator keeps the same console, with nodes, devices, usage and the audit log in one place, and the nodes are looked after the same way each time. A second node does not mean a second tool to learn.
If you want to plan the growth, start with the pilot, watch the capacity view for a few weeks, and add nodes when the numbers ask for it.
Questions
How many developers fit on one node?
It depends on the server and on the traffic. The capacity view shows the load on each node, so you see when to add another one.
Do devices move between nodes by themselves?
No. The administrator assigns devices to nodes. There is no automatic load balancing, and you stay in charge of who uses which node.
Can nodes stand with different hosting providers?
Yes. A node is any Linux server you own or rent, wherever it is hosted.
Does adding a node interrupt the others?
No. The new node is provisioned on its own while the existing ones keep serving.
Request a demo or a pilot
Tell us about your team, and we will come back with a time for a call and a plan for a pilot.