The packet, the log,
and the request.
Three programs, not one. Misaka decides what crosses your network. Kuroko tells you what it means. Uiharu answers the door. Nothing to route around.
$
Three programs, not one.
Each does one thing. Each ships on its own schedule. Each works without the other two.
SentinelX Misaka
Network control
Stands between your network and the internet. Decides what gets out, what gets in, and keeps the record.
- Closed source
- v1.0.0
SentinelX Kuroko
Log analysis
Reads everything Misaka records and tells you the few things worth looking at.
- CC BY-NC 4.0
- v1.0.0
SentinelX Uiharu
Request screening
Checks who is knocking before your application answers. Person or bot, customer or attacker.
- Closed source
- v1.0.0
Misaka
The part of SentinelX that actually stands between your network and the internet. Everything goes through it, and it decides what happens next.
- Enforcement
- Kernel space
- Closed source
- v1.0.0
Blocking that holds
Change the DNS, use a public resolver, type the IP by hand — none of it gets around the policy you set.
- Deep packet inspection
- TLS SNI identification
- Certificate fingerprints
- IPv4 / IPv6
Traffic goes where you say
Give any destination its own way out. Development traffic and business traffic never share a path.
- Policy-based routing
- Multi-egress balancing
- VLAN / VRF isolation
- Device authentication
Rules take effect now
Edit a rule in the console. Every device on the network is following it seconds later. Nothing restarts.
- eBPF kernel driver
- Hot update < 10ms
- Central policy store
- Version rollback
Nothing goes unrecorded
Every connection is written down and cannot be edited after the fact. This is what Kuroko reads.
- Tamper-proof chain
- ISO 27001 / SOC 2
- S3 / Elasticsearch
- 90-day hot retention
Ingress
The packet is captured on the way out, before anything can intervene.
Identity
Who sent it, from which device, and where it is headed.
Match
Checked against your policy. Block, allow, steer, or mirror.
Enforce
The decision is applied and the connection is logged.
Anything leaving your network is sorted on the way out and sent to the exit you chose for it.
NORMAL OUT
Clean traffic exits via primary WAN gateway
AUDIT OUT
Financial & social traffic routed to secondary interface and logged
BLACKLIST
Explicit / blocked content — sinkholed and logged
Kuroko
Millions of log lines go in. A short list of things worth your attention comes out.
- Analysis
- Misaka logs
- CC BY-NC 4.0
- v1.0.0
It learns what normal is
For every machine and every person on your network, separately. Nobody writes the rules.
- Per-host models
- Rolling windows
- Seasonality aware
It judges each one on its own terms
A quiet build server and a busy workstation are not held to the same number.
- Relative bands
- 0–100 anomaly score
- No global thresholds
It tells you the moment it matters
To your console, a webhook, or the SIEM you already use.
- Webhook
- SIEM export
- Severity routing
It shows its work
Every finding comes with the records behind it, so you can see exactly what it saw.
- Evidence bundles
- Replayable windows
- Immutable references
— sustained egress to three previously unseen destinations, 4.1× baseline volume, outside the host's normal activity window.
Uiharu
Every request is judged before your application ever sees it. Person or bot. Customer or attacker. Real click or replay.
- Judgment
- 0–100, four levels
- < 20ms inline
- Closed source
- v1.0.0
It looks at intent
Blocklists know what was bad yesterday. Uiharu decides about the request in front of it, which is how it catches things nobody has named yet.
- Behavioural scoring
- No rule authoring
- Adapts per route
It knows a bot from a person
Automated clients pretending to be browsers do not pass as people here.
- TLS fingerprinting
- Headless detection
- Pointer & timing signals
It knows where they really are
Even when the request is dressed up to look like it came from the same city as your customer.
- Residential proxies
- TOR exits
- Datacenter ASNs
It sees the campaign, not the request
Credential stuffing, scraping, carding, enumeration — these are patterns. Uiharu reads them as patterns.
- Cross-request correlation
- Velocity windows
- Campaign clustering
It rejects what is being reused
Replayed signatures, duplicated payloads, and links lifted onto somebody else’s site.
- Signature replay
- Origin binding
- Payload dedupe
It runs how you want it
Off, watching quietly, or blocking on its own. Your call, and you can make a different one per route.
- Off / monitor / block
- Per-route thresholds
- Zero integration
waiting for inbound requests…
- 94%
- of bad traffic never reaches you
- <20ms
- to decide, while the request waits
- 0
- lines of code to turn it on
By the numbers.
0.00%
Block accuracy
0μs
Policy latency
0ms
Risk verdict
0k+
Concurrent sessions
| Compared with DNS-level blocking | Traditional | SentinelX |
|---|---|---|
| Bypassable via DNS change | Yes | Impossible |
| Bypassable via DoH / DoT | Yes | Impossible |
| Bypassable via manual IP | Yes | Impossible |
| Traffic steering control | None | Granular routing |
| Behavioral anomaly detection | None | Kuroko, per-host baselines |
| Inbound request screening | None | Uiharu, inline |
| Audit log retention | None | Tamper-proof chain |
One system, one bill.
Every plan covers all three components plus the managed platform around them. All plans include a 30-day trial.
| Starter$299/mo | Enterprise$999/mo | Gov / MilitaryCustom | |
|---|---|---|---|
| Endpoints | Up to 200 | Unlimited | Unlimited |
| Precision domain blocking | Yes | Yes | Yes |
| Traffic steering | Basic | Granular | Granular |
| Connection log retention | 7 days | 90 days, tamper-proof | Custom audit chain |
| Deployment | Managed | Managed or on-premise | Air-gapped |
| Baseline modeling | Self-hosted | Managed | Managed |
| Anomaly scoring | Self-hosted | Real-time | Real-time |
| SIEM / webhook export | — | Yes | Yes |
| Request screening | — | Inline, < 20ms | Inline, < 20ms |
| Bot & automation defense | — | Yes | Yes |
| Custom rules & thresholds | — | Per route | Fully custom |
| Compliance reporting | — | ISO 27001 / SOC 2 | Dedicated assessment |
| Support | Community | 24/7 dedicated | On-site guarantee |
| Cryptography | Standard | Standard | FIPS 140-2 |
| Contact sales | Contact sales | Contact sales | |