§ 01 · The problem
Your customers' staff already use AI. Give them AI you run, with rules you set.
Your customers ask for AI. An agent for the team, an AI that keeps their documents private, a place for the app they built.
Their staff did not wait for an answer. In 2025, LayerX found that 77% of employees paste data into AI prompts, mostly from private accounts.
In Germany, 36% of companies used AI in 2025, up from 20% a year earlier (Bitkom). Almost half name data protection as an obstacle. Only 23% of German companies have rules for AI tools (Bitkom, 2025).
Say no, and they buy AI somewhere else. Part of the relationship you built goes with it.
Say yes on your own servers. AI Admin Panel gives each customer their own account and only the controls you allow.
§ 02 · The European picture
Data sovereignty is now a buying question in Europe.
GDPR and the EU AI Act add one question to every AI purchase. Where does it run, and who can reach the data?
| EU AI Act | The EU AI Act's bans have applied since February 2025. Most duties for high-risk AI now start in December 2027 or August 2028. |
|---|---|
| US CLOUD Act | Under the US CLOUD Act of 2018, a provider under US jurisdiction can be ordered to hand over data. This applies to servers in Europe too. |
| Microsoft France | In June 2025, Microsoft France told the French Senate under oath it could not promise French data would never reach US authorities. It added that it had not happened so far. |
| EU–US data deal | The EU–US data deal is under appeal at the EU Court of Justice. |
Data in an EU region can still be reachable under US law, if the provider has a US parent.
Run the AI on your own servers, and you can tell your customers where it runs and who has access.
AI Admin Panel gives you controls for your own assessment. It does not make a setup lawful by itself, so get legal advice.
§ 03 · In practice
Owning it means your servers, your rules and an AI route you choose.
Here is what that looks like in version 2.17.0.
Your servers
AI Admin Panel runs on its own Linux server, beside your cPanel or Plesk servers.
A local model
The AI requests stay on your server.
One account per customer
Each customer gets their own account and only the controls you allow. Each customer's apps share their own network.
Private from the start
Most new apps start private, behind the panel sign-in, until you publish them.
A route per app
For apps that support it, you choose the AI route at deploy.
Agents raise the stakes. A hacked website shows spam. A hijacked agent holds your customer's mailbox, CRM and keys.
A new agent starts private, behind your panel sign-in, on that customer's own network. Its passwords and AI keys sit in that customer's vault compartment.
With the customer's own key or your metered key, the requests go to an outside provider and leave your server.
§ 04 · Cost and change
Plan the cost, and keep your setup when AI changes.
Prices, terms and models change when the AI company decides.
A model on your own server costs you the server, rather than a fee for every question.
Apps and models change every quarter. The panel is the part that stays.
- Agents and apps Swap any time
- AI models Your choice, per app
- AI Admin Panel The part that stays
- Your servers Yours
§ 05 · For providers
You keep the customer, and AI becomes a service you sell every month.
The web reached small businesses through hosting providers. AI can take the same road, and you sit in the middle of it.
There are three things to sell: managed AI agents, managed private AI and a home for the apps your customers build. Each one is a service you can charge for every month.
A website earns a few euros a month. A managed AI service is worth far more to the same customer, and it renews every month.
You earn from a setup fee, a monthly care fee and AI usage on your metered key. Each customer gets their own budget. Your billing system still sends the invoices.
Once a customer's agent does real work, it stays. So does the customer.
Hosting providers
New monthly revenue from customers you already host.
MSPs
Managed AI in your portfolio, next to backup and security.
Agencies and AI professionals
Sell the build, then the care, every month.
§ 06 · Our mission
Every business will run AI. We want every business to own it.
The web gave every small business a website it owned. The next decade gives every business AI it owns.
What we're trying to achieve
AI that businesses own, run by providers they know.
A fair share of the AI business for hosting providers, MSPs and agencies.
Customer data on servers someone close to the customer controls.
§ 07
Good to know
- Meeting a law or standard depends on your whole setup. We make no legal or compliance promise, so get legal advice for your case.
- The panel and the server remain trusted parts of the system. Protect the server like any host with customer data.
- A local model must be installed and working. Speed depends on your hardware.
- Budgets cover only calls through your metered key. The panel doesn't issue invoices or collect payments.
§ 08
Sources
Each figure on this page comes from its primary source, checked on 29 October 2026.
- LayerX, now part of Akamai: Enterprise AI & SaaS Data Security Report 2025, 2025.
- Bitkom: Durchbruch bei Künstlicher Intelligenz, press release, 15 September 2025.
- Bitkom: Beschäftigte nutzen vermehrt Schatten-KI, press release, 21 October 2025.
- Official Journal of the EU: Regulation (EU) 2026/1744, 24 July 2026.
- US Code: 18 U.S.C. § 2713, added by the CLOUD Act on 23 March 2018, copy at Cornell Law School.
- French Senate, commission of inquiry into public procurement: record of the hearing of 10 June 2025.
- Official Journal of the EU: Case C-703/25 P, an appeal against the judgment in T-553/23, notice of 22 December 2025.