Skip to main content
FireSecurity

Early Access · pre-1.0 product

Try it without switching anything off.

FireSecurity runs next to your existing firewall in shadow mode: for every connection it reports what it would have done, and never touches the traffic. A modern firewall, logs and inventory to replace Kerio or pfSense: one panel, in Uzbek.

  • Traffic is not touched during the trial: the old firewall stays in place
  • The network keeps running after the license expires
  • In Uzbek, priced in Uzbek som, data on your own server
  1. 01

    Connect

    FireSecurity takes a copy of the traffic, through a switch port mirror (SPAN) or a transparent bridge. The old firewall stays where it is.

  2. 02

    Observe

    Traffic is not touched during the trial. You decide after you have seen the report.

    S06.1, S06.5 — netns lab

  3. 03

    Decide

    If you do not like the report, you stop, and there is nothing to switch off. If you do, you cut over by the runbook, with a confirmation window on every change and automatic rollback.

  4. 04

    The network keeps running after the license expires

    When the console is switched off, the license file is deleted, the license has expired or its signature is broken, real traffic is sent and lost packets are counted.

    QA-T-500 — on every change and every night

passeswould blockstopped

A sample network, drawn — not a measurement.

Live map

This is what traffic heading for your network looks like

Every day thousands of connections hit the edge of a network. FireSecurity stops them at the gateway itself and writes each one to the audit log. Spin the globe.

Simulation
This is an illustration: the arcs and counters simulate what a gateway in front of the sites would be doing. It is not measured telemetry, and the sources are anonymous points.

Blocked

0

Passed

0

Event stream

    Blocked trafficNormal traffic

    Who it is for

    Who are you? Each of you asks a different question.

    The administrator picks the firewall, the head of IT approves it, and the finance director or the rector pays for it. Each gets their own answer.

    Shadow trial

    See first, decide after.

    The objection a new vendor hears most is “risk”. Shadow mode takes that risk out of the trial: your existing firewall keeps working, and FireSecurity only observes and reports.

    1. Connect

      FireSecurity takes a copy of the traffic, through a switch port mirror (SPAN) or a transparent bridge. The old firewall stays where it is.

    2. Import

      A Kerio, pfSense or OPNsense configuration is imported. You get a report on every rule: migrated, approximately migrated, needs manual work or ignored — and why.

    3. Observe

      The report answers three questions: which traffic the new policy would have blocked, which traffic no rule matched, and which rules never fired at all. A daily summary arrives in Telegram.

    4. Decide

      If you do not like the report, you stop, and there is nothing to switch off. If you do, you cut over by the runbook, with a confirmation window on every change and automatic rollback.

    Not touching traffic is a test, not a promise. First we check that enforce mode really blocks, then that observe mode passes every packet unchanged. On a transparent bridge the outgoing frame is compared byte for byte with the incoming one.

    S06.1, S06.5 — netns lab

    Worth knowing: a port mirror sees addresses after NAT and does not model MSS differences. The panel states these blind spots itself, at the top of the report. Long observation on a real network will be measured in the first pilot.

    Migration › Shadow report
    The panel's shadow report: flows the new policy would have blocked but that carry traffic — rule, flow, number of flow logs, sources, and a decision button on each row
    A real panel screen. The data comes from a test set, not from a customer.

    Three answers to the new-vendor risk

    Shadow mode

    Traffic is not touched during the trial. You decide after you have seen the report.

    Exit guarantee

    Your data stays with you, and the contract says so. Today: the audit log, inventory and shadow report as CSV, and metrics in Prometheus format.

    Exporting the configuration as YAML and the logs in an open format is planned before 1.0.

    Early Access

    A discount off list and a free move to 1.0. Only modules proven in a pilot; the list is an annex to the contract.

    Request a shadow trial

    Traffic is not touched and nothing is switched off.

    Cost of ownership

    The license costs nothing. Owning it does.

    Our main competitor is not FortiGate but the free stack: pfSense or OPNsense, Zabbix, Grafana, Graylog, Wazuh. Its cost is not in the license but in administrator time. The calculation below uses only the numbers you enter; we add nothing of our own.

    The starting values are only an example. Replace them with your own.

    Stack and team
    Time
    Downtime and payments
    Risk — not converted into money

    Your current stack per year

    —

      This is the cost of your current stack. We do not promise in advance how much FireSecurity will save: in a pilot the same components are measured before and after, and the success criterion is written down at the start of the pilot.

      Request a trial with this calculation

      Honest comparison

      The free stack and FireSecurity

      A one-sided table convinces no one. The free stack is built from good tools, and the places where it wins are written down here too.

      CriterionFree OSS stackFireSecurity
      License priceZero its strengthAnnual subscription, in som; price on request
      FamiliarityAdministrators know it; plenty of guides and community its strengthA new product; the panel is in Uzbek, but it takes learning
      MaturityProven for years in thousands of networks its strengthPre-1.0, on Early Access terms
      Breadth of features todayBroader: IPS, SIEM, many plugins its strengthFirewall, NAT, multi-WAN, logs, inventory, audit; IPS in 1.0
      Install and upgradeEach tool is installed and upgraded separatelyOne install, one upgrade
      Login and permissionsSeparate in each toolOne login, roles, LDAP groups
      From incident to causeBy hand across tools, matching on time and IPFrom a log line to the rule and its version, in one click
      Firewall changesDepends on the tool; no single confirmation and rollback across the stackEvery change: view the diff, confirmation window, automatic rollback if not confirmed
      AuditEach tool has its own logOne hash-chained log, with a verification command
      Who to turn toA forum or paid support from abroadA local team, in Uzbek and Russian; best-effort SLA in Early Access
      Dependence on one personIf the person who built the stack leaves, the knowledge leaves with themOne documented product and its vendor
      Vendor lock-inNone — open source its strengthExit guarantee in the contract; part of the export is still on the roadmap

      When it is better to stay on the free stack. If your stack runs steadily, the person who built it is still on the team and it is documented, and what you need right now is IPS or SIEM correlation, do not rush. Today FireSecurity is strong not in breadth of features but in one panel and controlled change.

      Product

      What exists today, on real screens.

      Early Access covers the firewall and the daily work around it: rules, logs, inventory, audit and notifications. For the other modules, the release each arrives in is written down.

      Firewall, NAT, multi-WAN

      Zones and rules; the rule set is replaced in a single transaction. Several uplinks, health checks and failover.

      Logs and search

      Firewall verdicts and syslog from external devices. From any verdict line, go to the rule that produced it.

      Inventory

      A list of the devices the gateway has seen (ARP/NDP and DHCP), with CSV export.

      Migration

      Import from Kerio, pfSense and OPNsense; the shadow report; cutover and rollback runbooks.

      Notifications

      Telegram and email: WAN switchover, gateway offline, mode change, the daily shadow summary.

      Three languages, and the terminal

      The panel is in Uzbek, Russian and English. Every panel action is in the fsctl CLI too.

      Logs
      The logs screen: each verdict row shows the node, source and destination, the zone, and the name and revision number of the rule that produced it as a link
      On every log row the rule and revision are a link. One click from incident to cause.
      Commit-confirm
      The commit-confirm window: a countdown of the time left to confirm, a button to confirm the revision, and a note that without confirmation the gateway automatically returns to the previous revision
      An applied change waits for confirmation; if it is not confirmed, the gateway returns to the previous state by itself.
      Full roadmap: which module, and when
      ModuleWhenWhat it does
      Firewall Core, NAT1.0Zones, rules, NAT; the rule set is replaced atomically
      Multi-WAN1.0Several uplinks, health probes, automatic failover
      WireGuard VPN1.0Site-to-site tunnels
      Monitoring, metrics, dashboards1.0Node and interface state, uptime
      Logs and search1.0Verdict logs and external syslog, search and aggregation
      Inventory1.0A list of the devices on the network
      Proxy Manager, fsctl CLI1.0Reverse proxy; every panel action is in the terminal too
      Identity, NAC (monitor), DNS, DHCP, IPAM1.0 (Pro)Users, access control, address management
      IPS (Suricata-based)1.0 (Pro)Attack detection
      Server Manager, certificates, reports1.0 (Pro)Servers and PKI work
      PKI base, gateway HA, eBGP base1.0 (Enterprise)High availability and routing
      WAF (Coraza), config backup1.1Web application protection; configuration backup
      Remote access, password vault, NAC closed1.2Remote access and secrets
      TLS Inspect1.3Inspecting encrypted traffic
      ZTNA, MFA Server, JIT Access, SIEM correlation2.0Zero-trust and SOC foundations
      Fleet Manager, sublicensing (MSSP)2.0Managing many customers from one place

      Objection and answer

      What you will say, and our answer.

      Some objections are right. We admit them and offer a concrete condition instead.

      «The free tools already work»

      True, and they are good tools. The question is different: how many hours a year it costs you to keep them running. Run the calculation above with your own numbers; in a pilot we measure before and after.

      «A new vendor is a risk»

      That is why the trial runs in shadow mode: traffic is not touched and the old firewall stays in place. The exit guarantee is in the contract, and under Early Access the move to 1.0 is free.

      «No certificate»

      Correct: the product is not certified today, and we do not hide it. We start with organizations that do not require a certificate; for state universities, a trial deployment at no charge.

      «No references»

      Correct: the first pilot has not finished yet. So the first customers get a separate condition: a discount in exchange for the right to use them as a reference and case study, with an anonymous option.

      «Does the network stop when the license ends?»

      No. Forwarding, NAT, VPN, monitoring and logs do not depend on license state; only updates and support stop. This rule is checked on every change by a sabotage test.

      «Our network has no internet access»

      The product works without internet: logs and settings stay in your installation, and the license is activated offline. A complete offline installation bundle is not ready yet and is planned.

      «What hardware do we need»

      The intended class is an x86-64 server with 4 cores / 8 GB RAM / SSD for a small office, and 8 cores / 16 GB for a mid-sized organization. Throughput figures are not published until they are measured on reference hardware.

      «How does a pilot run»

      One organization, one site, one gateway: install and shadow mode, an observation period, then cutover and a rollback drill. The success criterion is written down at the start of the pilot.

      Trust

      What we have measured, and what we have not yet.

      In a security product, trust is built not from advertising but from claims you can check. Every item in the left column is guarded by a test. The right column holds what has not been proven yet, and so is not promised.

      Measured and tested

      • A license never stops trafficWhen the console is switched off, the license file is deleted, the license has expired or its signature is broken, real traffic is sent and lost packets are counted.

        QA-T-500 — on every change and every night

      • The rule set is replaced atomicallyThere is no “half-applied” state. The product does not touch the firewall rules of other software on the host.

        nft -c check and golden files

      • An unconfirmed change rolls back by itselfThe default confirmation window is 120 seconds. In a lab exercise, 0.4–0.6 seconds were measured from the rollback decision until traffic recovered.

        S02.5, cutover drill — in the lab

      • The audit log cannot be altered unnoticedAn entry that was edited, deleted, moved or truncated is found by the verification.

        fsctl audit verify — chain test

      • Shadow mode blocks nothingObserve mode neither changes nor drops a packet.

        S06.1, S06.5 — netns lab

      What we do not promise — yet

      • ThroughputThere are no throughput figures (such as “1 Gbit/s”) on this page: so far they were measured only in a virtual environment without a physical NIC, so they are a target, not a measurement.
      • No certificationThe product is not certified.
      • Independent reviewAn external pentest of the gateway and panel is planned and has not been done yet.
      • Pilot resultThe first pilot in a real organization has not finished yet; the long-term stability of shadow mode will be measured there.
      • Import coverageThe importers have been tested on sample files, not on a customer's real export, so we do not say “what percentage migrates”.
      • StatusThe product is pre-1.0; Early Access terms apply.

      This list gets shorter: when an item is measured, it moves to the left column and is updated here.

      Home — license expired
      The warning in the panel when the license has expired: license state does not affect traffic — firewall, NAT, VPN, routing, monitoring and logs keep running
      When the license ends, the panel says so: traffic, NAT, VPN, monitoring and logs keep running.

      Plans

      Priced by gateway and module, not per user.

      Price on request. The number of students or staff does not raise the price. During Early Access a discount off list applies, and the move to 1.0 is free.

      Start

      Small office, branch

      Price on request

      • Firewall Core, NAT, multi-WAN
      • WireGuard VPN
      • Monitoring, logs, inventory
      • Proxy Manager, fsctl

      Pro

      Mid-sized organization, university

      Price on request

      • Everything in Start
      • Identity, NAC (monitor), DNS, DHCP, IPAM
      • IPS (Suricata-based)
      • Server Manager, certificates, reports

      Enterprise

      Bank, large organization

      Price on request

      • Everything in Pro
      • PKI base, gateway HA, eBGP base
      • Four-eyes rule and an action budget

      In 1.1–2.0: WAF, remote access, TLS Inspect, ZTNA, SIEM correlation

      MSSP

      Integrators

      Price on request

      • Enterprise + Fleet Manager
      • Sublicensing, multi-customer reporting
      • Monthly billing

      From release 2.0

      Early Access terms
      ModulesOnly modules that have shipped and been proven in a pilot; the list is an annex to the contract
      Status“Beta”: the limitation of liability and warranty disclaimer are stated plainly in the contract
      PriceA discount off list; the move to 1.0 is free
      SLABest-effort: P1 response within 4 hours, during business hours
      SecurityInternal security review; an external pentest is planned and has not been done yet

      In every plan: Telegram and email notifications, the audit log, the rollback log.

      Next step

      Request a trial in shadow mode

      There is no form on this site: your message reaches us directly, and there is no button that falsely says “sent”. Write three things and we will plan together how the shadow trial connects:

      1. Your organization and network size (users, branches)
      2. Your current firewall and monitoring (Kerio, pfSense, Zabbix…)
      3. How you prefer to be contacted
      Request a shadow trial