EU AI Act compliance

The AI Act duties of your system, built into its code

Vstorm builds the technical side of EU AI Act compliance into agentic AI systems. We list the obligations that may apply to each system, build logging, human oversight and AI disclosure into it, and give your legal team the documentation.

30+ production deployments since 2017
Why AI Act work stalls

The policy is written. The system still cannot prove it.

Lawyers can say which duties apply. Engineers have to build the logs, oversight steps and documentation.

  1. 01

    Where it stallsNobody can list the AI systems the company runs.

    What we do We keep one inventory of each system, its role and its data.

  2. 02

    Where it stallsUsers are not told they are talking to AI.

    What we do We build the disclosure into the interface and the outputs.

  3. 03

    Where it stallsLogs exist, but no one can trace a decision.

    What we do We keep a log for every run, for as long as you set.

How we build it

Duties mapped first, then built into the system

One team reads the obligations and writes the code that meets them.

  1. 0103

    Which duties may apply

    We list your AI systems and map, for each one, the obligations your legal team should review.

    • Inventory of AI systems
    • Provider or deployer, per system
    • Obligations listed per system
  2. 0203

    Duties built into the code

    Record-keeping, human oversight and AI disclosure become features of the system, tested on every release.

    • Event logs for every run
    • Approval before consequential actions
    • AI notice in interface and outputs
    Automotive dealer group Accountants approve flagged and ambiguous document matches, and the models run in the client's own cloud tenant.
  3. 0303

    Records your legal team decides on

    Your legal team gets technical documentation, log samples and test results. Classification and any conformity assessment stay with them.

    • Technical documentation per system
    • Monitoring after launch
    • Runbooks for your team
Engineering in the open

We help build what agentic AI runs on

Open standards, open-source tooling and published research, all public, so you can check our engineering before you hire us.

Shaping agentic AI

Agentic AI Foundation

Vstorm was the first agentic AI engineering company to join the Agentic AI Foundation and received its 2026 Open Agentic AI Innovation Award.

Read the announcement

Open source

We build open-source agent tooling that other engineering teams install

9M+ PyPI downloads
3,900+ GitHub stars
31 public repositories

Framework contributors

When the framework breaks, we fix it at the source

We maintain our own open-source agent framework and contribute fixes to the frameworks our agents run on, through official partnerships with their teams. Breaking changes reach us before they reach your codebase.

Research

Our engineers and PhDs publish peer-reviewed research

Peer-reviewed papers on agent architectures, evaluation and AI security, and an open benchmark anyone can rerun against our results.

Track record

Frontier AI teams now build on what we shipped first

Our client agents were in production before most of today's agent frameworks had a stable release. You get a team that already knows what breaks between a promising demo and a system people rely on every day.

Engagement models

Ways to start

Each path starts with a free call with a founder or senior AI engineer. A build goes ahead only after its Proof of Value meets the agreed threshold.

FAQ

Questions about EU AI Act compliance

What does EU AI Act compliance mean for an AI agent? +
It depends on what the agent is used for and on your role. Most agents in customer service or operations carry transparency duties: people must know they are dealing with AI, and generated content must be marked. An agent used in an area the Act lists as high-risk, such as hiring, credit scoring or access to essential services, carries more, including risk management, data governance, event logs, human oversight, accuracy and robustness, and technical documentation. We map which of these may apply to each system, and your legal team confirms.
When do the EU AI Act obligations apply? +
In stages. Prohibited practices have applied since February 2, 2025 and duties for general-purpose AI models since August 2, 2025. Transparency duties under Article 50 apply from August 2, 2026. Providers whose generative systems were on the market before that date have until December 2, 2026 to mark the content they generate. The Digital Omnibus on AI, Regulation (EU) 2026/1744, moved the high-risk duties: December 2, 2027 for systems in the areas listed in Annex III, and August 2, 2028 for AI built into products covered by Annex I. Dates as of October 2026; your legal team should confirm them for your case.
Do you give legal advice or certify our system under the EU AI Act? +
No. We are engineers. We list the obligations that may apply to each system, build the technical side (logging, human oversight, disclosure, technical documentation) and give your legal and compliance team the records they need to decide. Classifying the system, and any conformity assessment, stays with your lawyers and, where the law requires one, a notified body.
Are we a provider or a deployer of our AI agent? +
If you build an AI system, or have one built, and put it into service under your own name, you may count as its provider, even when only your own staff use it. If you use a system someone else provides, you are a deployer, with fewer duties. The role decides the duties, so the inventory records it for every system and your legal team confirms it.
Our agent runs on GPT or Claude. Who carries the general-purpose AI duties? +
The model provider carries the duties for the general-purpose model itself. Your agent is an AI system built on that model, and its duties follow from how it is used: transparency for most agents, the high-risk set if it works in an Annex III area. We record which model and version each system uses, so a change of provider shows up in the documentation.
What does the AI Act require for logging and record-keeping? +
High-risk systems must record events automatically over their lifetime, so that results can be traced. We build that as a log per run: the input, the documents retrieved, every tool call, the output, the model version and who approved what. The logs stay in your environment and are kept for the period your legal team sets, which for high-risk systems is at least six months (Articles 19 and 26).
How do you build human oversight into an AI agent? +
The people overseeing the system need to understand what it does, spot when it goes wrong and be able to stop or override it. In an agent that means approval steps before consequential actions, a way to stop a run, the sources behind each answer on screen, and alerts when results drift. Which actions wait for a person is decided per system, with the team that will do the oversight.
What do we have to tell users about AI? +
Under Article 50, people must be told they are interacting with an AI system unless it is obvious, and synthetic audio, images, video or text must be marked as AI-generated in a machine-readable way. We build the notice into the interface and the marking into the outputs, and test both on every release.
Does this replace our GDPR or ISO 42001 work? +
It sits next to them. GDPR covers the personal data the system processes, and ISO/IEC 42001 is a management system standard for AI. The inventory, logs, oversight steps and documentation we build serve all three, so your teams do not keep separate records for each.
What do we have at the end of the engagement? +
An inventory of your AI systems with the obligations that may apply to each, the logging, oversight and disclosure code in your repository, tests for them in your CI, technical documentation per system and runbooks for the people who will look after it. All of it is yours to change, extend or take to another team.
When do we not need you? +
We only build tailored agentic AI systems, so we are biased. If your only AI system is a vendor's chatbot that you use as it comes, you are a deployer, and the vendor's documentation and your legal team may cover most of what you need. We are useful when you build your own system or have one built, or when an agent takes actions in your other systems.
AI Act review

Find the duties your AI systems already carry

Bring one AI system or a list of them. We map the obligations that may apply and what to build first.