Apply engineering rigor to AI-native development.Get the most out of AI in your company.
Ship production-ready software, from spec-driven development to final deployment, the right way and on the first attempt. The h|ve Platform plugs into your existing codebase, the standards your team follows and the enterprise tooling you already use.
A common layer between people and technology.
h|ve sits between the team and the stack: it takes direction from people and makes the same rule hold for every agent, model and tool.
Context
Goals, architecture, policy and owner become an executable base.
Orchestration
Agents, models and tools receive context and a sequence of work.
Integration
Data, repositories, boards, CI and systems stay where they already are.
h|ve Platform
Guardrails
Permissions, gates and policies travel with execution, not a checklist afterwards.
Observability
Every action gets origin, decision, deviation, execution, cost and evidence.
Portability
The stack can change without losing the layer that governs how it is used.
On top of the stack the company already has
- LLMs
- Agents
- RAGs
- Cloud and services
- Repositories
- Tests
Why h|ve matters
Without h|ve
Connected tools, fragmented operation.
Context gets lost between prompt, agent, PR, pipeline and approval. Governance tries to rebuild it afterwards.
With h|ve
One common rule follows all the work.
Context, authority, policy and evidence travel with the execution, whatever the tool.
Result
More speed without giving up control.
Context, authority, policy and evidence stay linked from the start to the result.
What the platform brings.
Six capabilities that act during execution, not in a review afterwards. Beside each one, the product screen where it shows up.
Context
Goals, architecture, policy and owners become a base the work consults and respects.
Inside the platform: the work.
The path of a card, from proposal to cost, on the real screens of the h|ve Platform. At each step, what the team sees and what the platform guarantees underneath.
01 · Intakeh|ve Flow
The machine proposes. A person decides.
On screen
Everything an agent suggests lands in Triage before it becomes work. For each proposal, someone on the team accepts it, marks it as a duplicate, rejects it with a reason or snoozes it.
Under the hood
Machine proposals stay apart from the team’s work until someone decides: the backlog only receives what a person accepted.
02 · The cardh|ve Flow
A card only moves along the allowed path.
On screen
The card drawer brings together the request, its fields, the refusals it has received and its stages. Under “Move stage”, the screen shows where it can go next.
Under the hood
The transition is a rule, not a convention: from Backlog, the only legal step is Spec, and the other stages show as blocked with the reason. The same rule holds on every channel: the board, the CLI or the MCP.
03 · The recordh|ve Ledger
One row per change, with who made it and under which rule.
On screen
Changes lists every card that changed in the period: who made it (person, machine or automation), the scope in files, the controls that ran and the outcome.
Under the hood
A pull request opened with no card, or a branch the gate recorded with no card, does not become a row: what shows up here went through the flow. The controls show, card by card, what was verified and what went ungoverned.
04 · The costh|ve Ledger
What each card cost, by model.
On screen
The Cost tab of the Trail adds up the period and breaks the spend down by card, with the model used and the tokens consumed.
Under the hood
The amount is estimated from a dated price base, and measurement has a declared start date. AI cost stops being the monthly invoice and becomes data on each delivery.
A platform that governs all your AI development.
Five modules around the same rule. Below, what each one does and what it asks of you.
h|ve Platform
MapBusiness
FlowBusiness and development
JudgeDevelopment and data
GuardDevelopment and governance
LedgerAudit
Context
h|ve Map
Business
- What it does
- Reads the documentation, the code and the decisions that already exist and distills all of it into a living model of your organization: capabilities, policies, owners and the rules the business actually follows. It is the semantic layer that gives AI the context it was missing, and it becomes the initial Flow configuration.
- What it asks of you
- The material you already have and a few hours from your leaders. Where documentation is missing, Map starts from reference models for your sector.
Orchestration
h|ve Flow
Business and development
- What it does
- Carries each piece of work from intent to merge across nine stages, with a gate at every handoff that only advances against the right artifact. The board moves on its own by the state of continuous integration. The merge stays a human decision.
- What it asks of you
- That work goes through the board, and that each gate has its artifact. The architect override is always at hand, and always asks for a recorded reason.
Drift analysis
h|ve Judge
Development and data
- What it does
- Compares the approved spec with what the pull request actually delivered and writes, on the PR itself, where the two drifted apart. Hardened against instructions hidden in untrusted content. Review starts already knowing where to look.
- What it asks of you
- An approved spec to compare against. With nothing agreed, there is no drift to point at.
Editor barrier
h|ve Guard
Development and governance
- What it does
- Lives inside the editor. The instant the agent tries to write, it checks whether that file belongs to the card approved for that branch. If it does not, the write does not happen. Not a warning after the fact, a block before it exists.
- What it asks of you
- One install line and a card with an approved scope. It costs 1.5 seconds per check, with per-branch caching.
Memory and trail
h|ve Ledger
Audit
- What it does
- Records every decision with author, authority and basis, in a history that only appends and never rewrites. Over time those decisions become the distilled memory of the company: an auditable trail that answers who decided, why and at what cost, and feeds business decisions.
- What it asks of you
- Nothing beyond working inside the flow. The trail forms on its own as decisions happen.
Native capabilities
Governed Context Layer
Decisions and execution
FinOpsAI
Cost and value at every level
BYOK
Control of LLM keys
LGPD + Immutable trail
Auditable evidence
Native governance. Without slowing delivery.
Inside the platform: governance.
After the work, what the company controls, proves and sends out of the product. The same real screens, read the same way.
05 · Governanceh|ve Map
What the company governs, and what it does not.
On screen
The Decision catalog matches 51 COBIT 2019 control points against what the company has configured, on three levels: the rule enforces itself, the decision is recorded, or nobody controls it.
Under the hood
A point with no answer shows as “not measured”, never as zero. The screen shows where governance already exists and where it is still only an intention.
06 · The proofh|ve Judge
The rule is proven, not promised.
On screen
Conformance shows the differential test: two independent implementations of the same decision, compared combination by combination.
Under the hood
It is not enough for both to deny: they have to deny for the same reason. In the latest proof, 952,320 combinations were compared with zero divergences, and the coverage of each axis is published without rounding.
07 · Outputh|ve Platform
Events go where the team already works.
On screen
In Settings, the project connects its GitHub repository (stage webhook, CI and automation) and registers outbound webhooks to Slack, Microsoft Teams or OpenTelemetry.
Under the hood
Before an address is registered, the platform sends a test event, and only a destination that accepted it is saved. API integration uses its own token, which can be revoked at any time.
The same feature crossing the five layers.
Build faster, with higher quality and lower risk, with specs as your single source of truth, advanced context management and consistent enforcement of the standards your team sets. The h|ve Platform brings rigor, quality and consistency so your teams deliver at their best.
use the arrow keys to walk the eight steps
The white dot in the corner of a gate marks the transition only a human credential opens: approving a spec, failing quality, authorizing an override and merging into main. A dashed line is a return, and it carries the colour of the piece that sent the work back.
The questions that come up before the conversation.
Does this replace my GitHub, my Jira or my editor?
No. h|ve governs on top of what you already use. The typical install removes no tool.
Do we need documented processes to start?
No. Half the cases start with no documentation. Map builds the first version of the model from reference frameworks for your sector and validates it with your leaders.
Will this slow my team down?
Barriers come in by choice, starting with one gate and two roles. Guard has a 1.5 second budget and lets the edit through if the service does not answer.
What is the AI not allowed to do?
To conclude on its own what requires human accountability. Approving a spec, failing quality and merging to the main branch require a person, with a person credential.
How much effort is the rollout?
Guard takes minutes. Flow in light mode takes less than a day. In Scan & Go, the first five phases add up to 14 working days with your leadership and selected teams.
We integrate your current stack.
Agents work inside your code hosting, task tracking, chat, cloud and continuous integration tools.
No replacing. No lock-in. No interruption.
AI
Development
Collaboration
Claude
ChatGPT
Gemini
VS Code
Cursor
GitHub
MCP
Microsoft Teams
GitLab
Linearh|ve Platform
h|ve Platform
AI
- Claude
- ChatGPT
- Gemini
Development
- VS Code
- Cursor
- GitHub
- MCP
Collaboration
- Microsoft Teams
- GitLab
- Linear
See the mechanism applied to your operation.
A short conversation to understand where your team is today and what the platform changes in your context. No generic demo: we start from your real flow.