Heyno Charter

This document reflects the strategy we have refined since Heyno began, including feedback from the people who run their businesses on it. The timeline to the hardware ahead remains uncertain, but our Charter will guide us in acting in the best interests of the people who hand us their work throughout its development.

Heyno’s mission is to make AI effortless to reach wherever work happens: one layer connecting any AI to your tools, your day, and the hardware ahead. We will attempt to build the assistant and the models beneath it ourselves, but will also consider our mission fulfilled if the AI you reach through Heyno is not ours. To that end, we commit to the following principles:

Ownership of the work

We commit to use any influence we have over how business data is stored and used to ensure the work remains the property of the person who did it, and to avoid enabling uses of that data that harm our customers or unduly concentrate power over them.

Our primary duty is to the businesses that run on Heyno. We anticipate needing to marshal substantial resources to fulfill our mission, but will always diligently act to minimize conflicts between our commercial interest and your ownership of your work: we do not train on your business data by default, you decide how long it is kept, and you can take it with you.

Human control

We are committed to keeping a person in control of every action with an effect outside the conversation, and to driving the broad adoption of that standard across assistants that act on a business’s behalf.

We are concerned about assistants acting on assumptions they should have checked. Therefore, anything that sends mail, delivers a quote, or moves money stops and asks before it happens, and where the assistant is unsure, the default is to escalate rather than proceed.

Openness at the edges

We will actively cooperate with the AI you already use; we seek an ecosystem in which an assistant earns its place by being useful rather than by being difficult to leave.

We are committed to keeping Heyno open at both edges. Today this includes speaking MCP in both directions, so Heyno can reach the tools your business runs and be reached by the model you choose, and we expect that openness to cost us retention from time to time, while increasing the importance of being worth staying for.

Sovereign deployment

To be effective for the buyers with the strictest obligations, Heyno must be able to run entirely inside their own walls; a promise in a contract alone would be insufficient.

We believe that some work should never leave the building: privileged legal material, records under a statutory duty, anything a regulator would ask about. For that work, Heyno runs on hardware the customer owns, inside the customer’s own network, where keeping the data in place is a property of the deployment itself.

Honest disclosure

We are committed to saying what the assistant is and what it is not. We disclose that it is AI on every call.

We will not publish a capability claim we have not measured. Where a benchmark appears on this site the method behind it appears too, and where a page is illustrative rather than a customer, it says so.