HelpifyrPlatform and operations
The controlled layer between people, AI agents and your systems.
This page shows what works beneath the surface: open modules, clear ownership, connectable systems and verifiable evidence.
01The principle
From request to controlled execution
Helpifyr holds the entire chain together, from request to evidence.
Request
An assignment becomes a clear next step, not a loose chat reply.
Rules
Roles, permissions, approvals and evidence are checked before critical steps.
Orchestration
Agents, workflows and existing systems are coordinated.
Approval
A person makes critical decisions.
Evidence
Decision, source, approval and result stay traceable.
02Connect
Connect, don’t replace
Helpifyr is not a rigid software suite. Existing systems are connected, extended or replaced step by step.
What exists stays
Email, ERP, CRM, documents, tickets and planning remain part of operations.
Gradual migration
Data and processes move piece by piece, without a big-bang switch.
Human decision
Approvals, escalations and responsibility don’t disappear into the AI.
03Architecture
Built in open layers
Each module has a clear task and clear boundaries.
Foundation
Fabric
Contracts, rules and governance for the whole system
Identity and keys
Heddle
Identity, sessions and SSO
Keystore
Protected storage for credentials and keys
Control
Warp
Orchestration and controlled execution
Pattern
Consistency and protection against drift
Execution
Shuttle
Running workflows
Wire
Delivery and external integrations
Tenter
Telephony operations with Asterisk and verifiable checks
Business logic
Spindle
Business rules and operational logic
Content
Loom
Controlled storage for documents and content
Memory
Bobbin
Persistent memory with proof of origin
Evolution
Dobby
Controlled adaptation and safe learning
Security and compliance
Beam
Checks security, updates and changes
Selvage
Compliance mapping, in preparation
04Already there
What is already concretely behind it
- Fabric
Binding rules via interfaces
Rules and contracts are published centrally instead of each module inventing its own.
- Spindle
Processes as events
Business processes are modelled through events, honestly scoped rather than as a blanket promise.
- Heddle
Sign-in and permissions
Login, session and SSO are unified instead of rebuilt per module.
- Spindle and Shuttle
ERP and workflows
ERP processes run on Frappe/ERPNext, workflows on n8n.
- Warp, Pattern, Beam
Control and security
Runtime control, mission control, review and security are cleanly separated.
- Operations
Runs on your own infrastructure
Designed for self-operation and verifiable readbacks, without platform lock-in.
05Changes
Every change is verified before it counts
- 01
Plan
An idea or problem becomes a clear assignment.
- 02
Bounded change
Changes stay small, are reviewed and have acceptance criteria.
- 03
Roll out separately
Merging into the code and rolling out are confirmed individually.
- 04
Verify live
What is checked is the state actually running, not just a green test.
06Open source
Open building blocks with substance
Frappe / ERPNext
Foundation for the ERP processes in Spindle.
Keycloak
Sign-in and SSO in Heddle.
n8n
Workflows and their operation in Shuttle.
OpenClaw
Runtime and verification paths for operations.
07Open Autonomy Spine
Weaveguard: checks before an agent acts
Weaveguard checks planned actions by AI agents against roles, policies, approvals and evidence before they are executed.
In preparation, not yet for production use
- 01An agent proposes a concrete action
- 02Roles, data sources and evidence are bundled
- 03Policies are checked
- 04The risk is classified
- 05Critical steps go to a person for approval
- 06Only permitted results move on
- 07Decision and approval are recorded
- 08The result is written back to Helpifyr in a controlled way
Want to go deeper?
The technical documentation shows every module in detail, or we can talk directly about your environment.