Agentic Index
Evoke Security vs Push Security (2026)
Evoke Security and Push Security both defend the identity attack surface where users actually work, at very different company stages: Push is the established player, sold through enterprise sales typically per user or endpoint with trials and assessments on request, hardening workforce identities against phishing and account takeover through the browser, while Evoke is a pre seed entrant with fast deployment across endpoint, proxy, and browser extension, demo led with no public pricing. Push is the dependable per user buy for workforce identity defense today; Evoke is a watchlist grade evaluation for teams that like being early.
| At a glance | Evoke Security | Push Security |
|---|---|---|
| Category | Security / SOC agent | Security / SOC agent |
| Entry price | No public pricing; the site directs buyers to contact Evoke. Pre seed, enterprise sales led with a demo based motion. | Not public; enterprise sales, typically priced per user or endpoint |
| Free / trial | Demo on request; no public free tier | Free trial or assessment available on request; no public self serve tier |
| Pricing confidence | contact only | contact only |
| Feature | ||
|---|---|---|
| Action & orchestration | ||
|
Integrations & Tool Calling Ability to connect agents to real systems through native integrations, OAuth-authenticated actions, custom tools, APIs, webhooks, or MCP-compatible tools. |
Full / Explicit | Full / Explicit |
|
Workflow Orchestration Ability to sequence, branch, retry, route, and combine deterministic workflow nodes with autonomous agent steps. |
No / Not documented | Partial |
|
Triggers & Channel Coverage How agents wake up and where they work: schedules, webhooks, message events, CRM events, inbox events, chat, email, voice, and collaboration tools. |
Partial | Full / Explicit |
| Knowledge & context | ||
|
Knowledge Grounding & RAG Ability to ground agent behavior in company data through document ingestion, retrieval, external knowledge APIs, semantic search, or RAG layers. |
Partial | Full / Explicit |
|
Memory & State Persistence Ability to persist context across a run, conversation, workflow, user, team, or longer-term memory layer. |
Partial | Partial |
| Control & trust | ||
|
Human Oversight & Guardrails Approval steps, consent checkpoints, escalation rules, structured guardrails, policy constraints, and pause/resume controls. |
Full / Explicit | Partial |
|
Security, Identity & Governance RBAC, SSO, auditability, encryption, least-privilege tool access, compliance posture, and data handling policy. |
Full / Explicit | Full / Explicit |
|
Observability & Auditability Traces, logs, execution histories, metrics, audit events, and debugging detail for production agent behavior. |
Full / Explicit | Full / Explicit |
|
Deployment & Data Residency Deployment modes and options, including SaaS, dedicated cloud, VPC, on-prem, hybrid, local runtime, and self-hosting. |
Full / Explicit | Partial |
| Solution readiness | ||
|
Prebuilt Agents, Templates & Packs Ready-made workflows, packaged employees, templates, blueprints, industry solutions, and role-specific agents that reduce time-to-value. |
No / Not documented | Full / Explicit |
| Platform extensibility | ||
|
Model Flexibility & Routing Ability to work across multiple foundation models, route tasks to different models, or let buyers bring their own providers and keys. |
No / Not documented | No / Not documented |
|
APIs, SDKs & MCP Extensibility Composability layer: stable APIs, SDKs, MCP tool consumption/serving, custom tools, and integration into internal systems. |
Partial | Partial |
|
Testing, Debugging & Optimization Testing, debugging, scoring, retries, fallbacks, quality gates, and optimization loops for improving agent workflows before and after deployment. |
Partial | Partial |
| Specialist automation | ||
|
Browser & Computer Use Browser, desktop, or remote/local computer control for workflows that cannot be handled through stable APIs alone. |
No / Not documented | Full / Explicit |
Pricing snapshot
Sourced from the Index pricing dataset · open each vendor's profile for full detail.
| Pricing | ||
|---|---|---|
|
Entry price Lowest public entry point |
No public pricing; the site directs buyers to contact Evoke. Pre seed, enterprise sales led with a demo based motion. | Not public; enterprise sales, typically priced per user or endpoint |
|
Pricing confidence How public the numbers are |
Contact only | Contact only |
|
Billing Primary billing axis |
enterprise license, likely by agents or environments monitored | users or endpoints |
|
Variable cost Workload / overage exposure |
Medium variable cost | Low variable cost |
|
Free tier / trial Try before you buy |
No free tier
|
No free tierTrial
|
|
Buying motion Self-serve vs sales call |
Sales call | Sales call |
Choose Evoke Security if
- You are willing to evaluate a very early vendor for potential capability edge.
- Multi surface deployment across endpoint, proxy, and browser appeals.
- A demo costs nothing and your risk tolerance allows pre seed vendors.
Choose Push Security if
- Predictable per user pricing sized to headcount fits your budget.
- Browser based identity attack defense is the proven scope you need.
- An established vendor with trials and assessments derisks deployment.