Platform
Agents decide. Documents become data. Bots do the clicks.
Three modules on one platform — AI Agent Management, Document Intelligence and RPA Bot Orchestration — with a person in the loop across all of them, a Partner Hub for the agencies that resell it, and three ways to run it: our cloud, a hosted dedicated environment, or your own infrastructure.
Three modules, one run log
Metered by Workflow runs
AI Agent Management →
AI Workflows: a browser builder with 700+ integrations, triggers, approvals and agents that use tools — MCP servers and your own bots included. Bring your own LLM (OpenAI, Anthropic, Google, Azure, self-hosted).
Metered by Document streams and pages
Document Intelligence →
IntelliDocs: describe the document and the fields, get JSON. No templates, no model training, handwriting included. Validation rules and a person where needed before anything reaches the ERP.
Metered by Bot runs
RPA Bot Orchestration →
Deterministic bots for SAP GUI, AS/400, Citrix, desktop apps and portals, built in Studio, run unattended on Bot Runners (unlimited available), orchestrated from the cloud, callable by agents.
Bot Runners, users, integrations and workflows are never metered. Agents use your own LLM key; document intelligence and Easley AI credits are included. How pricing works →
A person in the loop — in every module, not a separate product
Approvals, forms, tasks and reviews are steps inside the workflow, the document stream and the bot — logged in the same run. How approvals and forms work →
In AI Workflows
Approval actions for Slack, Teams, Gmail, Outlook and Telegram; native forms and tasks assigned from a flow; a Human Input step for chat. The flow waits, then continues with an audit entry.
In Document Intelligence
Validation rules on extracted fields and a review step for whatever fails them — a person validates where needed, the rest goes straight through.
In RPA
Bots pause for a sign-off before a consequential step and resume with the answer recorded; every run keeps a console log a person can replay.
How a process moves through it
The same five steps in every production flow we see — whether the trigger is an invoice in an inbox, a ticket in a PSA or a message on WhatsApp. The agent and the bot are different tools for different parts of the job; the person stays where the consequences are.
- 01
Trigger
A schedule, a webhook, an email with an attachment, a form, a chat message, an SFTP drop, an app event — or another agent via MCP.
- 02
Agent decides
Reads the document or the context, classifies, extracts, drafts, picks the next tool. Structured output, maximum steps, visible reasoning.
- 03
Document becomes data
IntelliDocs returns the fields; a workflow validates totals and references; a person validates where needed.
- 04
Bot does the clicks
Where the target system has no API, a bot enters the data on screen — unattended, logged, on a Bot Runner.
- 05
Person approves
Anything consequential pauses for a decision in Slack, Teams or email; the run continues with the answer recorded.
For consultancies, integrators and MSPs
Partner Console & Hub
A tenant per client
Orchestrator tenants with security groups and cross-team access keys; client workspaces for AI Workflows are in development.
White-label
Bot Runner and portal under your brand today; Studio and orchestrator white-labeling being extended with self-service settings.
Playbooks, training, deals
Sales and marketing playbooks, Campus certification, deal registration with margin per deal, a demo environment for a named client.
Three ways to run it
Same platform, same modules. What changes is where it runs and who administers it. Bot Runners are Windows applications on your machines in every option; no model is trained on your data in any of them.
ElectroNeek Cloud
Multi-tenant SaaS on Microsoft Azure with SOC 2 Type II controls, SSO with Google and Microsoft, roles, security groups and audit logs. Bot Runners stay on your machines.
Trust Center →Hosted
A dedicated environment hosted and administered by ElectroNeek in the region you choose — isolation from other customers without infrastructure to run.
Hosted plan →Sovereign Suite
The whole platform — orchestrator, bots, document intelligence and the LLM you choose — installed inside your own infrastructure, white-labeled, with isolated tenants.
Sovereign Suite →