Enterprise
A missing control, added without disruption.
HEIP runs alongside your identity, bot and fraud tools. Start by watching, enforce one action at a time, and keep a record of every decision.
Your tools each answer a different question
| Layer | The question it answers | You probably have |
|---|---|---|
| Identity checks | Who is this person? | KYC, ID and selfie checks |
| Sign-in | Can they prove they own the account? | passwords, MFA, passkeys |
| Bot management | Does this traffic look automated? | edge and network bot tools |
| Fraud scoring | Does this transaction look like fraud? | risk engines, transaction rules |
| HEIP | Is a person in control at the moment of this action? | the missing row |
HEIP works alongside every row above. It replaces none of them. Use its answer on its own, or as one more input to the decision you already make.
Identity and KYC
tells you who opened the account. HEIP tells you a person is using it now.
Bot management at the edge
filters traffic. HEIP judges the specific action inside the session.
Fraud scoring
looks at the transaction. HEIP looks at who, or what, is at the controls.
Use HEIP's answer as one signal in your existing decision, or as a gate on its own.
NIST SP 800-63B-4 recognises session monitoring as a risk-reduction measure after sign-in. NIST SP 800-63B-4
Roll out without risk
Observe mode
Per site or per action. HEIP never blocks; you see what it would have done.
Step up before deny
Uncertainty becomes a step you control.
Per-action policies
Strict where it matters, invisible elsewhere.
Your fail-safe choice
You decide what happens when HEIP can't be reached.
Guided onboarding, one action at a time
Onboarding takes 6 to 8 weeks on your first workflow and compares your current stack alone with your stack plus HEIP. HEIP runs in observe mode (sometimes called shadow mode), so nobody is blocked while you measure.
Week 0
Scope
Pick one high-risk action. Agree how results will be measured and what success means. Privacy and security questions answered.
You get: A written rollout plan with go-live criteria
Week 1
Baseline
Document how that action is protected today and what outcomes you see.
You get: A baseline to compare against
Weeks 2-5
Observe
HEIP decides on real traffic in observe mode. Nobody is blocked.
You get: HEIP's decisions next to your current outcomes
Weeks 5-6
Compare
Review decisions and reasons together against agreed, labelled scenarios. Tune the policy.
You get: A comparison report
Weeks 6-8
Decide
Switch that action to enforce once the agreed criteria are met, then plan the next action.
You get: Enforcement live, and a plan for the next action
What we measure together
| Measure | Question |
|---|---|
| False step-ups | How often would real customers have been asked for an extra step? |
| Added detection | What did HEIP catch that your current controls didn't? |
| Customer friction | Did completion or abandonment change on that action? |
| Speed | How much time does the check add at the action? |
| Integration effort | How many engineering hours did it take, and what does it need to run? |
Go-live criteria are agreed before launch and written into the rollout plan. For example: added detection above an agreed level, at a false step-up rate below an agreed ceiling, with no measurable drop in completion.
Guided onboarding is included with Enterprise.
Audit and governance
- Decision records
- Every decision is recorded with its outcome, reasons, policy and mode. History stays in the dashboard for 30 days.
- Investigation detail
- A detailed record of each decision is available for live investigation for 1 hour.
- Audit log
- Every configuration change (sites, domains, keys, policies, users) is kept in an audit log for 365 days. Policy changes are recorded there too.
- Roles
- Owner, admin and member roles. Team invites and SSO are coming soon.
- Isolation
- Your data is never visible to another customer.
Deployment
| Option | Status |
|---|---|
| HEIP Cloud | Available now |
| Dedicated environment | Coming soon. Ask your account team. |
Security review
For your security review, we provide:
- The security overview, with what HEIP receives, never receives and how long it keeps it
- A call with the engineers who build HEIP
- A review of how detection works, under NDA
Trust has to move with the action.
Tell us which actions you want to protect. We'll come back with a rollout plan and a quote.