Client-controlled environment
Deploy in a client-controlled environment or dedicated tenancy.
Security & Architecture
ZERO INTEGRATION NEEDED
Every integration you add is risk you must manage.
Most AI vendors sell system-to-system integration first. Helm is different by design: it automates human-to-human work with zero integration — so the security exposure and risk that come with connectors simply don't exist. You get the same outcome — in fact better, with agentic AI — without replacing a single member of your staff.
A / Integration-first AI
Security and risk built into the model.
- 01
Deep system credentials
Integration-first AI needs privileged access to your ERP, CRM and core systems.
- 02
Deployment takes months
From kickoff to the first real automated task, integration rollouts run on months — not days.
- 03
Long, fragile rollouts
One broken connector can stall the entire automation programme.
- 04
Replacing staff — causing layoffs
Integration-first AI automates people out of the process, so your team sees it as a threat, not a tool.
- 05
Security risk. Data risk.
Credentials, pipelines and copies of your operational data — every layer adds exposure.
B / Helm · Zero integration · Zero exposure
Plug and play.
The risk is none
- 01
Works where people already are — WhatsApp, Telegram, Teams, Slack, email
- 02
No system credentials requested, stored or managed to start
- 03
Plug and play — potentially live within a day
- 04
Same outcome as system-to-system automation — in fact better, with agentic AI
- 05
Empowers your staff to deliver — never replaces them
Helm automates human-to-human coordination, not system-to-system plumbing. You get the outcome of automation without handing over system access.
No connectors to your core systems. No new attack surface. No security review to get started.
Security
Built for enterprise environments.
Governance, access and auditability are part of how Helm works — not an afterthought. And because Helm starts with zero integration, none of the security and risk of system-to-system AI applies — while your people keep doing the work, better.
Stateless processing architecture
Processing designed so data is not retained beyond what the work requires.
Role-based access
Permissions scoped to roles, departments and locations.
Audit trails
Every instruction, reminder, approval and submission is logged.
Governance history
A complete, reviewable record of how work was driven to completion.
Secure integration architecture
Least-privilege connections to enterprise systems.
Enterprise access controls
Supports SSO and centralised identity management.
Data governance
Configurable retention, ownership and deletion controls.
Frameworks & regulatory considerations
PDPA
Designed around PDPA considerations
GDPR
Designed around GDPR considerations
ISO 27001
Aligned controls
SOC 2
Aligned controls
RMiT
Aligned architecture where applicable
References to frameworks describe alignment and design intent. They do not represent certification unless expressly stated.
Company security perimeter
Your systems.
Your security perimeter.
Your apps and databases stay inside your organisation. The gateway masks personal data before processing and restores it when the answer returns.
Company architecture
Masking gateway · Stateless processing · Zero retention
Your perimeter
Inside your organisation
People
WhatsApp · Web · Email
Helm
Company tenant
Core systems
Read-only access
Operational apps
Line of business
Department devices
Private local AI
Operational database
Encrypted at rest
Results return here
Your people stay in control
Masked request
Masking gateway
Tokenise on send
Restore on return
TLS 1.3 · Audit
Permitted result
Helm cloud
Processing layer
AI models
Reasoning · Agentic
Compute
GPU · Scaling
Orchestration
RBAC · Audit
Stateless
No retention
Helm infrastructure
Tenant isolation · Scaling
Data ownership
Customer-controlled data
Masked responses
Returned through the gateway
Your organisation
One company tenant connects your departments. Systems and raw data remain within your perimeter.
The gateway
Masks outbound data, restores returned answers and records the exchange.
Helm cloud
Processes masked requests without storing or retaining raw client data.
Reference deployment architecture. Masking, retention and processing controls are configured and validated for each environment. The standard zero-integration product does not require system connections.
Optional connections
Three ways to connect.
API for direct access. MCP for shared tools. RPA when there is no API. Every connection is permissioned and audited; the standard zero-integration product needs none.
Low effort
API
Connect directly
Helm uses a system’s published interface to access approved data and operations.
Best for
Systems with a published API
Direct access. Lower maintenance.
Medium effort
MCP
Connect through tools
Helm discovers approved tools through a shared standard, with permissions set by each server.
Best for
Many tools through one standard
One standard. More connections.
Medium–high effort
RPA
Work through the screen
An automation tool operates an existing interface when the system has no API.
Best for
Legacy apps and desktop portals
A fallback. More maintenance.
Open standards · zero lock-in
No lock-in. Ever.
We deliberately build on public industry standards instead of private formats. Your data stays in your systems, and the work stays yours.
01 / Ownership
Your database, your server
Data sits in your own environment — on-prem or your private cloud. Helm reads and writes; it never becomes the system of record.
02 / Ownership
Open, public standards
Standard SQL, REST/OpenAPI, MCP, webhooks and open file formats. No proprietary schema, no encrypted black-box store.
03 / Ownership
You own the workflows
Every workflow, prompt, rule and integration is exportable in readable form. What we build with you belongs to you.
04 / Ownership
Leave whenever you want
No exit fee, no data ransom. Turn Helm off and your data, history and workflow definitions remain intact and usable.
Standards we build on
PostgreSQL / SQLREST + OpenAPIMCPWebhooksOAuth 2.0 / OIDCSAMLCSV / Parquet / JSONSFTPiCalSCIM