Edyssa
Network and production infrastructure, from the internet line to the application, for school management software.
- Client
- School management software for daycares and preschools
The problem
Edyssa needed to run its applications on hardware it owns: a reliable internet connection, a network that keeps production apart from testing, and releases that do not depend on anyone logging in to a server.
What we built
- The network: dual WAN with automatic failover, and a centrally managed router, firewall and switching
- Separate networks for public, production, testing and management traffic, with firewall rules between them
- Two virtualised servers: one for production, one for testing
- Administration only over a private VPN, with key-only logins
- A release pipeline from code merge to running server, with uptime checks and alerts
From the internet line to the application.
We set up the network as well: the connections, the routing, the firewall and the segmentation the servers rely on.
- InternetDual WAN with automatic failover
Two internet lines. If one drops, traffic moves to the other automatically, so the platform stays reachable.
- GatewayBusiness-grade router and firewall
Routes between the internal networks, enforces the firewall rules between them, and hosts the VPN.
- ControlCentrally managed network
The router, switching and network policies are configured and monitored from one controller.
- SwitchingManaged switching
Each server receives only the networks it needs; management traffic is kept separate.
- SegmentationSeparate networks by purpose
Public, production, testing and management traffic each have their own network, and connections between them are denied unless a rule allows it.
- ServersVirtualised hosts on Proxmox
Production and testing virtual machines run on separate physical servers, each on its own network.
How it is set up
- Production and testing separated
- Separate servers and networks. Testing cannot reach production.
- Network segmentation
- Public, production, testing and management traffic each on their own network.
- VPN-only administration
- Servers are managed over a private VPN with key-only logins.
- Automated deployments
- Merges build container images in CI and roll out to testing without anyone logging in.
- Monitoring and alerting
- Every service is checked each minute; the team is alerted when one fails.
- Self-hosted, cloud-portable
- Runs on hardware the company owns; the same images can move to a cloud provider.
Outcome
Every merged change is built once and rolled out to testing automatically, and production runs the exact build that was tested.
Discuss a similar project.
Describe the process. An engineer will review it and get back to you. No obligation, no sales pressure.
Talk to an engineer