Margin
flat rate, not per token
The problemAI features on a per-token API erode the margin of the plan they ship in.
HelmcodeA fixed monthly rate per key turns AI into a known cost, not a variable that grows with adoption.
industries · SaaS
AI features without giving up your margin.
Shipping AI features shouldn’t erode your margin. A flat rate gives you cost predictability instead of variable per-token pricing, the number your CFO actually wants.
the economics
The economics, by design.
Each cost lever mapped to a platform capability. Sovereignty comes by default.
Predictability
a fixed line on the P&L
The problemThe CFO is part of this purchase and hates usage surprises.
HelmcodeFrom a flat monthly rate, no per-token surprises and no long-term lock-in.
Sovereignty
EU · white-label
The problemYour customers’ data flows through your product, and its compliance is yours.
HelmcodeEU-only inference, zero logs and an OpenAI-compatible API you can white-label with confidence.
whose obligation is it
When your logo makes the system yours.
A SaaS product puts its own name on top of somebody else’s model. Article 25 is about exactly that move, and it names three ways a company that thought of itself as a customer becomes the provider, with the obligations that come attached.
01
Three ways to become the provider
Article 25(1) treats a distributor, importer, deployer or other third party as the provider of a high-risk system if they put their name or trademark on one already on the market, make a substantial modification to it, or change its intended purpose so that it becomes high-risk.
02
The one upstream has to help
When that happens, paragraph 2 obliges the original provider to cooperate closely with the new one, making available the necessary information and the reasonably expected technical access. Unless it had explicitly stated the system was not to be turned into a high-risk one, in which case you are on your own.
03
A written agreement, with one exception
Paragraph 4 requires a written agreement between the provider of a high-risk system and whoever supplies the components or tools inside it, specifying information, capabilities and technical access. It excludes third parties making tools available under free and open-source licences.
EU AI Act · Regulation (EU) 2024/1689 Regulation (EU) 2024/1689 of 13 June 2024, Article 25, paragraphs 1, 2 and 4. Whether your product is high-risk at all is the prior question, decided by Article 6 and the annexes, and it is one for your legal team rather than your infrastructure provider. read the report →
use cases
Your most common use cases.
The cases with the most traction in the sector, each with its own page in detail.
Semantic search & recommendation Semantic search inside your product, at flat cost across every customer. Professional copilots In-app copilots grounded in each customer’s own data. Document extraction Structured data extraction as a feature, at volume. Summarization Summaries of activity, tickets and documents inside the product. Classification & triage Tagging, routing and prioritising inside the product, where cost per action decides whether the feature ships. Synthetic data Staging and demo environments that stop running on a copy of your customers’ production data.
Recommended open models.
A starting point per task type. The full guide maps 80 cases to the open model for each one.
- DeepSeek V4 Flash in Helmcode
- The flat-rate workhorse for in-product AI at any volume.
- Qwen 3.6 in Helmcode
- The best open writing for in-product copy and Spanish-first products.
- qwen3-embedding + rerank in Helmcode
- Semantic search and recommendation as a core feature.
We are distilling and quantizing these open models into small, tightly specialised versions, trained for one task rather than for all of them. A model like that runs on less hardware, answers faster and fits where the big one does not, your own datacenter included. If you have a process with volume and stable criteria, that is the conversation we want to have with you.
// faq
Questions, answered.
What the sector's technical, compliance and business teams ask.
Why not just use a per-token API?
Because the AI feature’s cost then scales with adoption and erodes the margin of the plan it ships in. A flat rate per key makes the cost predictable, which is what lets you price the feature confidently.
Can we white-label it?
Yes. The API is OpenAI-compatible and runs on EU infrastructure with zero logs, so you can embed it in your product and answer your customers’ privacy questions cleanly.
How predictable is the cost?
A fixed monthly rate per API key, from €399/month, with no per-token surprises and no long-term commitment: a single fixed line on the P&L.
How fast can we integrate?
Change the base URL and key; OpenAI-compatible SDKs and frameworks keep working unchanged. Most teams are in production the same day.
// get started
START BURNING TOKENS
Skip the AI infra work. Deploy your first private inference endpoint today.
Flat rate. EU data. OpenAI API compatible.