Hane Platform

What is Hane Platform

An overview of the AI business platform on which business apps and AI agents run on shared data, workflows, approvals, and audit.

This page explains what problem Hane Platform solves, who it is for, which pieces it is made of, and how those pieces fit together.

The problem it solves

When you build each business app on its own, you rebuild data storage, approval flows, permissions, and audit records for every app. Once AI agents join the work, you also have to decide what the AI may read, who approved an outgoing email or phone call, and whether you can trace afterwards what happened.

Hane Platform is an AI business platform that provides these as shared services. Your business apps and AI agents run on the same business data, workflows, approvals, and audit. What you build per app is only the screens and the logic specific to that business.

Business data is stored according to the types and fields you define. Every value carries a value state (confirmed, estimated, pending inquiry, or unknown) and a source that says where it came from.
You define how work proceeds as a workflow. Human decisions and work are assigned to people as tasks.
When an AI agent proposes an operation with an external effect (sending email, placing a call, updating an external system), it runs only after passing the approvals your policies require.
Every operation is recorded in the audit log: who did what, under which permissions.

Hane does not force a common data model or UI on its customers. Types, workflows, and approval rules are defined per customer in manifests; the execution, authorization, and audit machinery is shared.

Who it is for

Reader	What they mainly do
Developers at customer companies	Build business apps with the public API, the SDK, and hanectl, and manage definitions such as types and workflows as manifests
Organization administrators	Manage members and roles, service accounts and API keys, apply a suspension when needed, and review the audit log
Business users and operators	Work on tasks in business apps or the Console, make approval decisions, and follow the progress of cases

Main pieces

Piece	What it is
Platform services	Services for organizations, business data, definitions, workflows, approvals, agents, documents, communication, integrations, audit, and more. Each has a public API under `/v1/<service>/...`
Console	The web UI for organization administrators, developers, and operators. You view definitions and what is running, and perform operations such as approval decisions, retrying failed cases, and suspension
SDK and hanectl	Call the public API with the TypeScript SDK (`@hane/sdk`). hanectl is the CLI that validates, diffs, and applies manifests, and creates, promotes, and activates ReleaseBundles
Hane Cowork Preview	A desktop app that runs on the user’s PC. It uses the platform’s authentication, models, and organization settings to carry out work with local files and the browser

How they fit together

  Your business apps ──┐
  Console ─────────────┤
  hanectl / SDK ───────┼──▶ Public API entry ──▶ Platform services
  Hane Cowork ─────────┘    (auth, rate limits)   business data, workflows, approvals, agents, documents ...
                                                    │
                                                    ▼
                           Shared foundation: authorization, secrets, usage, audit

Your business apps, the Console, and hanectl all call the same public API. The Console has no back door: actions taken in the UI pass through the same authorization, approvals, and audit as API calls.
Definitions such as types, workflows, approval rules, and agents are written as YAML manifests kept in Git, and applied with hanectl or synced from Git. The Console does not change definitions.
Your business apps read and write business data, cases, and tasks through the public API.

An example of work on Hane

Taking vehicle lease management as an example, work proceeds on Hane like this:

Every morning a schedule looks for lease contracts whose notice deadline is approaching and starts a case for each contract.
If some values are not confirmed (for example, an estimated end date), the workflow creates a task for the person in charge to check them and waits until they are confirmed.
An agent drafts a comparison of the cost of each option, and the person in charge decides the direction in a task.
Operations with an external effect, such as applying to the leasing company, proceed only after approval by the department head, or by the department head and then accounting, depending on the amount.
When the case completes, an outcome is recorded, and every decision and operation along the way remains in the audit log.

Every piece of this flow (the schedule, the workflow, the tasks, the agents, and the approval rules) is defined in manifests.