» DEPLOYMENT
Deployment that fits into how your network already works.
» On-premise or cloud — which one fits you
On-premise
Cloud
Where your flow data lives
In your own infrastructure
On our secure collector
Time to first visibility
Same-day installation with our engineers
Minutes after redirecting your exporter
Local hardware needed
Server or VM per the sizing guide
None
Best for
Teams with data retention or sovereignty rules
Teams who want to start without provisioning hardware
» On-premise
From setup to live visibility.
In 4 steps.
- 125 min · You
Infrastructure provisioning
Prepare a VM per the sizing guide.
- 2120 min · Our engineers
System installation
Nothing to do on your side — we install remotely with temporary access.
- 315 min · You
Flow export setup
Point your routers' NetFlow/IPFIX export to the collector — we guide you.
- 430 days · Together
Active validation
Full-feature trial, no traffic or feature limits — we validate data and detection with you.
Your team's time: about 40 minutes — steps 1 and 3.
Sizing guide
- CPU16 cores (32 vCPU)
- RAM64 GB
- StorageHDD
- CPU48 cores (96 vCPU)
- RAM128 GB
- StorageHDD
- CPU16 cores (32 vCPU)
- RAM64 GB
- StorageHDD
Bigger network or mixed traffic? We size it with you
» Cloud
Faster access.
Lighter local footprint.
For teams who want rapid visibility without running the full platform locally.
- 125 min · You
Source configuration
Point your edge router's NetFlow/IPFIX export to our secure public endpoint.
- 230 days · Together
Access & analysis
Instant access to your hosted Grafana dashboards — monitor from day one.
» DATA COLLECTION
How the data reaches FLOWCUTTER.
Flow export from your routers
Your existing devices export NetFlow, IPFIX or sFlow to the collector IP. No inline appliance, no rerouting.
Software flow probe
Where a device cannot export flow, our software-based probe reads traffic passively from a SPAN port or TAP.
SNMP metrics alongside
Interface and capacity metrics from SNMP complement flow data in the same Grafana dashboards.
Works with MikroTik, Cisco, Juniper, Huawei, Arista, Nokia and any device exporting NetFlow, IPFIX or sFlow.
Your data, your rules.
After the pilot, we stay with you.
Once data is flowing, we tune detection thresholds together with your team so alerts match your real traffic. Our engineers stay reachable directly — not through a ticket queue.
Common questions
Where is our data processed? Does it leave our network?
On-premise: no. Flow data stays in your infrastructure, with no call-home traffic, and you control retention and access. Cloud: flow data is sent to a FLOWCUTTER-hosted collector in EU data centers, encrypted when you use a VPN tunnel.
Does cloud deployment have any limits?
A few. Your router needs a public IP. A VPN tunnel (IPsec or WireGuard) is optional but recommended for encrypted transport. The vulnerability scan is not enabled by default. For very high traffic volumes, choose on-premise.
How much traffic can FLOWCUTTER handle?
One instance handles up to 100 Gb/s of unsampled traffic; sampled traffic scales further — see the sizing above. Larger networks scale horizontally with additional collectors.
Which devices and vendors are supported?
Anything that exports NetFlow, IPFIX or sFlow — Cisco, Juniper, MikroTik, Nokia, Huawei, Arista and others. FLOWCUTTER also reads BGP sessions and DNS. Open standards, no vendor lock-in.
Do we need to change our network architecture?
No. FLOWCUTTER is fully passive — nothing inline, no impact on forwarding or routing.
Who deploys it and how long does it take?
Our engineers, remotely with your team. On-premise installation takes about 2.5 hours, but only around 40 minutes of that needs your team — FLOWCUTTER engineers handle the remaining 2 hours. Cloud setup is just a router configuration that takes about 25 minutes of your team’s time.
How does licensing work?
Based on your traffic volume. Transparent, no hidden fees, and no lock-in after the trial.