Know who is really connecting to your servers
GPS trackers, alarm panels, TURN users, mail and SSH logins identify themselves with nothing but a claimed ID. Prynt Gate records every connection, checks that claim against the identity's history of networks, carriers and countries, catches enumeration, cloned identities and brute force, and decides allow, flag or block, with a score and the reasons. A small agent applies the blocks to nftables or ufw.
Available. Available today: in production and ready to use.
Free plan, then from $49 / month · 14-day free trial
From a log line to a decision
-
1
Collect
The agent reads Traccar, sshd, mail, TURN or alarm-receiver logs, or Vector and Fluent Bit ship them, to /v1/gate/events.
-
2
Decide
Each connection is enriched offline (country, ASN, VPN, hosting, Tor) and scored by detectors and your rules: allow, flag or block.
-
3
Act
The bouncer blocks the source in nftables or ufw with a TTL; webhooks, email, Slack and Telegram alerts tell your team.
Why it matters
-
An identity for every device
Every IMEI, alarm account, username or SSH key becomes an entity with its history of IPs, ASNs, carriers and countries, so a claim can be checked against what that identity normally looks like.
-
Spoofing caught, not just logged
Unknown-ID bursts, the same identity from two places at once, a new carrier or country, impossible travel, auth-fail bursts and port scans are detected as they happen.
-
A log you can trust
Every event is appended to a hash chain per account and environment. There is no edit or delete API; retention leaves a checkpoint so the chain can still be verified.
Capabilities
Every line has its own status, so you can see what exists today and what is still planned.
POST /v1/gate/events with a per-sensor token or the environment's secret key: up to 500 events per request, idempotent by eventId, JSON, JSON array or NDJSON.
A stable entity per claimed identity (imei, panel_account, username, email, ssh_key_fp, turn_user and more) with its network timeline, and one per source IP.
Country, city, ASN and operator, VPN, hosting/datacenter, Tor and abuse-list flags from the same offline datasets Prynt Identify uses. No third-party lookup per event.
Enumeration of unknown IDs, auth-fail bursts per source and per identity, concurrent sources, new ASN or country, impossible travel, first seen, port scans, scanner signatures and device identities from Tor, VPN or hosting.
A 0–100 score with reasons on every event, thresholds you set, and an allowlist (LAN, router, monitoring) that is never blocked.
The same declarative rules as Identify: WHEN field op value THEN allow, flag or block, by priority, with an evaluate mode that only counts would-be matches.
Applies block decisions to nftables or ufw with a TTL, honours the allowlist, and runs in dry-run mode until you switch it to enforce.
Traccar (connections and unknown devices with IMEI and IP), SIA DC-09 receivers, sshd, fail2ban, Stalwart mail, coturn and generic JSON, tested on real log samples.
Ready-made sink configurations, or POST raw lines to /v1/gate/logs and Prynt parses them with the same parsers.
Hash-chained, append-only, with retention per plan and a verification endpoint.
Grouped alerts with a cooldown, sent by email, Slack (incoming webhook) or Telegram (your bot).
gate.decision, gate.block.created, gate.block.revoked and gate.alert, HMAC-signed like every Prynt webhook.
Separate environments with their own sensor tokens, events, rules and blocks, so a test sensor never blocks production traffic.
Prynt Gate stores the full source IP of each connection: blocking an attacker needs it. Identities are the values your devices claim; Gate never contacts the devices or the networks behind them.
Pricing
Free plan with 2 sensors, 250,000 events a month and 7 days of history. Prynt Gate Pro is $49 a month with a 14-day free trial: 10 sensors, 10,000,000 events a month and 90 days of history. Self-serve checkout for Pro is not open yet: to move to Pro today, write to [email protected].
- 10 sensors
- 10,000,000 events / month
- 90 days of history
Billed monthly through Stripe, on your Prynt account. All plans on the pricing page
Use cases
-
GPS tracking platforms
Trackers send their IMEI over Teltonika or GT06. Gate flags an IMEI that shows up from a second network while the device is still connected, and blocks sources that try one IMEI after another.
-
Alarm receiving centers
Panels report with an account number over SIA DC-09. Gate learns each account's usual network and flags a report from a new carrier, country or a hosting provider.
-
Mail, SSH and TURN
Auth-fail bursts against Stalwart, sshd or coturn are blocked at the firewall, and a login that succeeds from a new network is flagged for review.
How it connects to the platform
Gate uses the same account, team, roles, audit log, webhooks and billing as the rest of the suite, the same offline IP intelligence as Identify and the same declarative rules engine. Its webhooks can start Prynt Automate workflows.
How the platform connects- Identify's IP intelligence: country, ASN, VPN, hosting and Tor, offline.
- The same rules engine: field, operator, value, action, priority.
- Webhooks signed with HMAC, so Automate or your own backend can react.
- Same account, team, permissions and Stripe billing.
Frequently asked questions
Is Prynt Gate available?
Yes. It is in production today. Sign up with the Gate option or activate it from Products in the console; the free plan needs no card.
How is it priced?
Free: 2 sensors, 250,000 events a month, 7 days of history. Pro: $49 a month with a 14-day free trial, 10 sensors, 10,000,000 events a month and 90 days of history. If Pro ends, the account keeps working on Free.
What is a sensor?
A machine or service that sends events: the Prynt Gate agent, a Vector or Fluent Bit pipeline, or your own connection log. Each sensor has its own token, allowlist and mode.
Does Gate block on its own?
Gate decides; the bouncer agent applies blocks only on hosts where you install it, and it starts in dry-run mode. Allowlisted addresses, such as your LAN or router, are never blocked.
How is it different from fail2ban or CrowdSec?
fail2ban and CrowdSec are mature, free tools that block on log patterns, and CrowdSec adds a community blocklist that Gate does not have. Gate adds an identity layer: it tracks the ID each device claims across networks and flags the same identity from two sources, a carrier change or impossible travel. It can also read fail2ban's own log.
What data does Gate keep?
Each connection event with its full source IP, the claimed identity, port, protocol, network details and decision, for the history days of your plan (7 on Free, 90 on Pro). Events are never edited; retention deletes the oldest.
See who connects to your ports
Create an account, add a sensor and install the agent in dry-run mode. The free plan needs no card.