INATE™ Platform Access Security
Verify a human at the
millisecond of commit.
The upstream, pre-bind gate that verifies human presence at the exact moment an action commits.
INATE™ Powered — the Hearts sequence. A timed tap pattern, read upstream at the execution boundary before your backend commits, bound to the exact payload and recorded in a signed receipt.
CAPTCHAs are broken and MFA gets bypassed. iPAS is the upstream, pre-bind gate that verifies human presence at the exact millisecond of commit.
Automated scripts, bots, and AI agents hit an upstream wall. Humans are approved at the boundary, issued a signed, tamper-evident receipt, and passed through before any execution touches your database.
Simple, usage-based scale. No minimums, no commitments. Plug in the API, secure the actions that matter, and only pay for verified approvals.
Who iPAS is for
If a bot or agent can act, trigger, commit, or execute, iPAS belongs in front of it.
Why they need iPAS
Every downstream control fails at the boundary:
- CAPTCHAs
- MFA
- Identity
- Biometrics
- Behavioural inference
- Bot-monitoring
None of them gate execution itself. iPAS does: the Hearts sequence sits upstream, before the payload commits.
The core truth
Upstream execution
iPAS sits at the execution boundary, before your backend commits.
Pre-commit verification
It verifies a live human is present before the action binds, not after.
Signed receipt
It issues a tamper-evident, Ed25519-signed receipt your backend checks before executing.
Upstream gate
The Hearts sequence is required to pass the boundary, before compute is ever authorized.
iPAS isn’t a bolt-on security feature. It’s a control at the execution boundary.
Pricing
Usage-based. You only pay for verified human approvals. No minimums, no commitments.
- 0 – 1M verifications10¢ / verification
- 1M – 5M5¢ / verification
- 5M – 100M3¢ / verification
- Over 100M1.5¢ / verification