Chat
Talk, and Heym builds and tests it.
Describe a job by typing or by voice. Heym asks the few questions it needs, builds the workflow, runs it with sample data and marks it Verified.
Verified
Lead intake
Tested 1 time before it was saved.
Enterprise AI Systems & Solutions
We design, build, and operate AI-powered business solutions tailored to your workflows, with custom interfaces, integrations, and human oversight.
Powered by Heym Core, our self-hosted agentic runtime.
Heym Work/Lead intake
Example workflowChat
When a lead emails us, save it to the Leads table, draft a reply and ask me before it goes out.
Verified
Lead intake
Tested before it was saved.
Run by Heym Core, on your infrastructure
Why Heym Work
AI becomes valuable when it fits the way your business actually works. Heym Work brings AI-powered workflows, custom interfaces, integrations, and human oversight into one operational experience, powered by Heym Core.
The problem
Generic chatbots and disconnected automation tools work in a demo. In daily operations they don’t fit your processes or systems, teams can’t run them on their own, and IT can’t see what they do.
Very quickly, this leads to:
“Most fail due to brittle workflows, lack of contextual learning, and misalignment with day-to-day operations.”
With Heym Work
We adapt AI systems to your processes, existing tools, and team requirements rather than forcing your operations into a generic workflow.
Give business teams practical interfaces to manage tasks, review AI-generated results, and move work forward without interacting with the underlying automation engine.
Run AI-powered processes on your infrastructure with human approval, execution visibility, and evaluation capabilities supported by Heym Core.
Our Solutions
We turn complex business processes into practical AI-powered systems, tailored to your workflows, connected to your tools, and designed for your team.
Automate document processing, information extraction, case management, and review workflows while keeping people involved in important decisions.
Examples
Connect your existing systems, coordinate multi-step processes, and manage tasks and approvals through tailored AI-powered workflows.
Examples
Help teams manage customer requests, research accounts, and coordinate service and revenue operations with AI-powered workflows.
Examples
Starting points, not fixed products: we shape each system around your process. Your team works in Heym Work, and Heym Core runs it underneath.
Worked examples: Knowledge and Policy SystemsHuman-in-the-Loop AI OperationsMulti-Agent Orchestration
What changes
No canvas to learn: people describe the work and get a workflow Heym has already tested, then run it from the pages they use every day.
In the example: Sales asked for lead intake in one sentence and got a Verified workflow.
A glass box, not a black box: each run lists its steps, its duration and the instance that ran it. Engineers open the same run in traces, with tokens and cost.
In the example: The Acme Logistics run took 5.1s and ran on worker-2.
Agents draft, people decide: approval steps pause a run before an email goes out, a record changes or money moves, and roles decide who may do what.
In the example: The reply waited until someone approved the draft.
Heym Work
Heym Work provides the business-facing environment, while our team builds and integrates tailored AI solutions around your specific processes. Teams can also use it on their own: people describe the job, answer a few questions, and work from pages built for them, with Heym Core running the workflows underneath. To evaluate it yourself first, request a Heym Work trial.
Chat
Describe a job by typing or by voice. Heym asks the few questions it needs, builds the workflow, runs it with sample data and marks it Verified.
Verified
Lead intake
Tested 1 time before it was saved.
Pages
Numbers, tables with status chips, charts and file drops, built by describing them. A row opens its own page for that one record.
New leads this week
11
Acme Logistics
Opened from the table: its own page, its own widgets.
Leads by day
Last 7 days
Approvals
When an agent pauses for a person, the review waits in Activity and on the page. Approve, request changes or reject, and the run continues.
The agent drafted a refund of 240 EUR and paused for a person to decide.
Next in the queue
Roles and sign-in
Owners, Editors and Viewers, with the company sign-in your Heym Core already uses. New members start as Viewers.
One workflow, end to end
The example above, step by step. The same four steps hold for a contract review, an invoice exception or a student request.
01 · Heym Work Chat
Someone writes or says what they need. Heym asks the few questions it has, builds the workflow, tests it with sample data and marks it Verified.
02 · Heym Core
Each new lead starts a run. The agent reads the email, saves the lead and drafts a reply, while Heym Core runs it in the background on your servers.
03 · Activity · Tasks
The run pauses before anything goes out. The reviewer reads the draft and approves it, asks for changes or rejects it.
04 · Activity · Runs
The reply goes out, and the run stays in Activity with every step, its duration and the instance that ran it.
Start with Heym Work in one minute. Below it, the Heym Work film follows a lead from the first request to a drafted reply, and the others install Heym Work, work in its Legal edition and build one flow across Slack, Google Sheets and email.
Heym Work in one minute.
From the first agent that works to AI in every team: build workflows, run them, follow every run and approve what matters. Shown on the Legal edition.
Editions
Explore how Heym Work can be adapted to different industries. Each solution is tailored to the workflows, systems, and requirements of your organization.
Six editions for industries and four for the teams every company has: IT, Sales, Marketing and HR. Each edition is a starting point: it opens with pages, tables, workflows and templates for that work, so a team begins with screens it recognizes.
Legal
Contract operations
Counsel
Chat
Tables
Knowledge
Drive
Activity
What do you want Heym to get done?
Contracts awaiting review
3
AI reviews by risk
Contracts triaged by risk, research and drafts grounded in your own playbooks, and lawyer decisions in one Approval Desk.
See Legal templatesYour infrastructure
Heym Work and Heym Core run where you run them: on-premises, in your VPC or air-gapped. When the load grows, add Heym Core instances as workers on the same database. Each run records the instance that ran it.
Heym Work
Commercial license
The interface your teams use
Chat·Pages·Approvals·Activity
Every action goes through Heym Core’s access rules
Heym Core
Free, source-available
The runtime that runs and governs every job
Execution·Traces·Evals·Single sign-on·Audit log
Heym Work keeps its own tables in a separate schema of the same database
Self-hosted data storage
Workflows, run history and encrypted credentials, kept in your own database
What leaves your network
Model providers and tools you connect
They receive what your workflows send them. Point models at Ollama or vLLM to keep inference inside your network.
heym.run
Heym Core asks for the newest release. Heym Work sends a daily license report: license ID, installation ID, active users in the last 30 days, total members, runs in the last 24 hours, and versions. Networks without internet access use an offline license.
Heym stores workflow content, inputs, outputs, run history and credentials only in your database.
Already running Heym Core? Heym Work is set up in three steps.
Start Heym Work
One container starts next to your Heym Core, on the same database, with the industry edition your team works in.
Connect Heym Core
A Heym Core admin opens Settings, Heym Work, enters Heym Work’s address and generates a key.
Run the setup
Enter the license key, connect Heym Core with its address and the key, and sign in as an Owner. Home opens, ready for the team.
Controls
Most of these controls are part of Heym Core, which is free to self-host. Heym Work builds on them: people sign in through Heym Core, and every action Heym Work takes passes Heym Core’s access rules.
Owner, Editor and Viewer. New members start as Viewers.
| Roles | Viewer | Editor | Owner |
|---|---|---|---|
| Open pages and run workflows | |||
| Answer their own reviews | |||
| Build workflows and widgets | |||
| Manage credentials and traces | |||
| Manage the license and updates |
Always on. Secrets never reach a line, and the trail goes where your logs already go.
[winston.audit] action=auth.login outcome=successactor_email=dana@acme.example
[winston.audit] action=credential.update outcome=successtarget_name="CRM" config_changed=true
[winston.audit] action=work_integration.key_rotate outcome=successactor_email=it@acme.example
[winston.audit] action=auth.token_refresh outcome=deniedreason=refresh_token_replayed_or_revoked
Security and compliance
Encryption keys rotate on your schedule, credentials stay in the vault your company already runs, and access ends the day someone leaves.
Key rotation without downtime
Credentials are encrypted at rest. Change the encryption key whenever your policy asks, while workflows keep running.
The vault you already use
On Kubernetes, credentials come from HashiCorp Vault, AWS Secrets Manager, Azure Key Vault, Google Cloud Secret Manager, CyberArk and 20+ other secret managers.
Secrets kept out of storage
Credentials from your vault stay in memory, outside Heym’s database and its backups, and an update in the vault applies without a restart.
Two-factor sign-in
Password sign-in asks for a code from an authenticator app, and new users set it up with a QR code before their first session. SSO keeps your provider’s own MFA.
Production Pilot
A production pilot is a focused first step toward a custom AI solution, allowing both teams to validate the approach before committing to a broader implementation. Together we select a high-value workflow, build a tailored solution, integrate the necessary systems, and validate the results. The pilot is optional: when the scope is already clear, we can go straight to implementation.
A defined scope, clear success criteria, and a practical path to production.
Understand your existing workflow, business challenges, systems, and success criteria.
Develop a working AI-powered solution with relevant integrations, tailored interfaces, and human oversight.
Test the solution with your team, evaluate results against agreed criteria, and identify improvements.
Define the next steps for production deployment, operational ownership, and ongoing support.
How we work together
Custom Development & Services
We design and implement custom AI systems around your business processes, from tailored workflows and interfaces to integrations with your existing tools. Powered by Heym Core and supported by our engineering team.
Your business requirements, our engineering expertise. We build tailored AI systems, operational interfaces, and integrations designed for real-world workflows.
Deploy Heym Core and Heym Work on your infrastructure, working with your IT team or ours.
Maintenance, troubleshooting, updates, and further development under an agreed support arrangement.
Help your teams adopt and manage the solution through practical onboarding, documentation, and knowledge transfer.
Services are scoped and quoted separately from seats. See pricing
Each answer names the mechanism behind it.
Still have a question?
Ask us about your setup, your security review or your rollout. A person from our team replies.
Talk to our teamor write to enterprise@heym.run
Heym Core is free to self-host under its source-available license, and it includes single sign-on, audit logging, traces, evaluations, human review steps and multi-instance execution. Heym Work, the interface for business teams, needs a commercial license priced per paid seat. Enterprise agreements add volume pricing, priority support and SLA terms, security and architecture reviews, and deployment help.
See pricingHeym stores workflow content, inputs, outputs, run history and credentials only in your database. Data goes out in three cases: your workflows send it to the model providers and services you connect, Heym Core asks heym.run for the newest release, and Heym Work sends heym.run a daily license report. That report holds the license ID, an installation ID, the number of active users in the last 30 days, the total number of members, the number of runs in the last 24 hours, and the Heym and Heym Work versions. Model inference can stay inside your network through Ollama or vLLM endpoints.
In your Heym Core database, on your infrastructure. Heym Work reads what it shows from that database and keeps its own few tables in a separate schema of the same database.
Yes, with an offline license on request.
Ask for an offline licenseHeym Core keeps running every workflow, schedule and webhook. Online licenses renew through the daily sync. If that sync fails for 30 days, a 14-day grace period starts, and after it the Heym Work interface asks an Owner for a new key. A trial runs through its last day and reopens when our team extends it, with one trial per installation.
Yes. Heym supports single sign-on through OpenID Connect against your own identity provider. Keycloak, Okta, Entra ID, Auth0, Google, and any other OIDC provider connect from a single issuer URL, using Authorization Code with PKCE and an encrypted client secret, and a connection test verifies the setup before rollout. Accounts can be limited to your own email domains, password sign-in can be switched off once SSO is verified, and Heym Work uses the same sign-in.
Read the single sign-on setup guideViewers open pages, answer their own reviews, ask questions and run workflows in Chat, and read data. Editors also build workflows and widgets, share and manage them, change data, and manage traces, credentials and MCP. Owners also manage the license and updates. New members start as Viewers.
Yes, always on. Heym writes an audit line for every privileged action with the actor, the target, and the outcome as success, failure, or denied. Failed logins and refused access are recorded as exactly that, and secrets stay out of the trail. The trail streams alongside your container logs, so any log driver, collector, or SIEM picks it up with the pipeline you already run.
Read the audit logging referenceCredentials are encrypted at rest in your PostgreSQL database with Fernet, and the encryption key rotates without downtime and without re-entering a credential. Heym uses MultiFernet, so every instance first learns the new key for decryption, then the new key takes over encryption while the old one still reads existing values. An admin re-encrypts every stored value in the background from Settings and retires the old key once that shows Completed. A key check at startup stops an instance that holds the wrong key, and in a multi-instance cluster only instances whose keys fit receive work or lead. Rotation protects the backups taken after it, so after a suspected leak, rotate the credentials at their providers as well.
Read how key rotation worksYes, on Kubernetes. Heym reads credentials from labelled Kubernetes Secrets, so External Secrets Operator can supply them from HashiCorp Vault, AWS Secrets Manager, Azure Key Vault, Google Cloud Secret Manager, CyberArk and more than 20 other secret managers, in line with the secret management your company already runs. SealedSecrets and SOPS through Flux or Argo CD work the same way. Values stay in memory, outside Heym’s database and its backups, and a change in your vault reaches Heym without a restart. These credentials appear read-only with a Kubernetes badge, work in every node like any other credential, and are shared with users and teams from the Secret’s annotations.
Set up credentials from Kubernetes SecretsYes. Additional Heym Core instances join as workers against the same PostgreSQL database and share workflow execution through weighted load balancing you control, adjustable without a restart. Leader election keeps cron schedules, alert evaluation, and crash recovery running through a failover, and every run records the instance that executed it.
Read the load distribution guideHeym Core’s source is public, so your team can read the runtime code rather than rely on a vendor questionnaire. A review typically covers single sign-on against your own identity provider, credentials stored encrypted in PostgreSQL and referenced by name, encryption key rotation, credentials read from your own vault through Kubernetes Secrets, role-based permissions, the audit trail, and self-hosted deployment inside your own perimeter. Heym Work’s connection to Heym Core is documented, and Enterprise agreements include support for security reviews.
Talk to us about a security reviewBook a demo, request a Heym Work trial or plan a production pilot. Tell us which process you have in mind, and we tailor the conversation to it.
Prefer email? Write to enterprise@heym.run.