Software development
Portals and dashboards
Customer self-service portals and internal dashboards on real data.
Architecture
Architecture
- 01Map the processHow it is done today, and where the time goes
- 02Working versionA small usable slice, not a full specification
- TypeScript
- Next.js
- PHP
- 03IntegrateWith the existing systems, on real data
- REST API
- webhooks
- PostgreSQL
- 04ShipDeploy, logging and monitoring from day one
- Docker
- nginx
- CI/CD
- 05OperateFixes and improvements against real use
- Logging
- Metrics
- 06HandoverCode, documentation and deployment on your side
Capabilities
Capabilities
Every item is marked: verified production experience, or engineering capability.
Our own NOC console (OpenPath)
ProvenLive path monitoring, an incident feed and per-ASN filters — written because no off-the-shelf product answered the question. In daily production use.
- in-house
- probes
- per-ASN
An ISP billing system
ProvenSubscriber lifecycle, tariffs, balances, SMS and reporting — serving a live operator.
- billing
- provisioning
- SMS
Web platforms and portals
ProvenTypeScript/Next.js and PHP — server rendering, bilingual content, a CMS and access control.
- Next.js
- TypeScript
- PHP
- PostgreSQL
API integrations
ProvenMoving data between systems: monitoring, IPAM, billing, ticketing, payments.
- REST
- webhooks
- cron
Automation and scripting
ProvenRepeating operations turned into a script, then into a service — with nobody running it by hand.
- Python
- Bash
- Ansible
Mobile and desktop clients
CapabilityWhere a web interface is not enough.
Technology stack
Technology stack
- Frontend
- TypeScriptNext.jsReactTailwind
- Backend
- Node.jsPHPPythonREST API
- Data
- PostgreSQLMySQLRedisClickHouse
- Infrastructure
- DockernginxCI/CDAnsible
Engagement model
Engagement model
Project
A one-off scope: audit, migration or implementation with a fixed outcome.
Retainer
Monthly engineering hours — specialist access on demand.
Co-managed
NetWizard and your in-house team together, with split responsibility.
FAQ
FAQ
Do we own the code?
Yes. The code, the documentation and the deployment procedure go to your side — lock-in is not part of the model.
How is this different from a normal dev shop?
We operate networks, billing and monitoring ourselves. There is no requirements-translation step — we already understand the problem.