Solutions
Use cases, sizes & pilot
One page with three views: where Amastan fits, which pack to pick, and how the lab pilot works.
Use cases
Where self-hosted control matters most — government, telecom, and regulated teams.
Banking & financial services
Government & critical networks
Telecom & managed security
Evaluate in your lab
Pick a size that matches your team
Amastan is sold by how many people browse through it — not by confusing cloud meters. Small teams can start free; larger companies get backup machines and more headroom.
What we mean by “user”
Packs at a glance
Open source for small teams
Not sure which size?
Pilot offer
60-day paid pilot
Prove self-hosted allow / block / RBI on your traffic — with operator workflows and audit evidence your team can review.
What you get
A focused evaluation — not a multi-year platform rollout.
Pilot appliance access
Sanitized Pilot RC1 environment (lab deploy / gated VM) with operator console.
Prove core verdicts
Allow, block, and optional Remote Browser Isolation on representative URLs.
Evidence pack
Logs, dashboards, and a joint review of what worked / what to harden next.
How the pilot runs
1Scope: sites, identity source, success criteria, and constraints (air-gap, residency).
2Deploy the appliance in your lab and connect a controlled traffic path.
3Run scenarios: known-good, known-bad, grey-zone, and operator troubleshooting.
4Review outcomes with your network / SOC team and decide next steps.
What we need from you
- A lab owner (network or security) and a short weekly check-in
- Representative destinations / categories to test (sanitized list is fine)
- Directory access for identity tests if you want user-aware policy
- Clear go / no-go criteria before week 1
The pilot focuses on a self-hosted web filter. Bigger cloud security suites and multi-site fleets are on the roadmap — we stay honest about that.
Request a pilot
Tell us about your environment. Your message is emailed to us — we reply from [email protected].