Sovereign AI · Built for Europe

Sovereign AI,
built for Europe.

Alveraign is a Europe-centric, decentral AI platform. We help organizations use AI without losing control of their data, their decisions, or their direction.

Why we do what we do

The short version: because intellectual property and operational sovereignty still matter — and because Europe deserves to take part in the AI revolution on its own terms.

Integrity and sovereignty were meaningful, tangible values to us decades before these words became IT-business jargon. That's also why we're fascinated by the ability to build electronic "brains" for the benefit of all. And the problems coming along with that huge leap concern us equally.

Over the years we saw tremendous efficiency gains in our IT landscapes. We also saw growing dependencies — vendor lock-in, data lock-in — arising for individuals and organizations, as soon as they had fully adopted a once-frontier IT technology. Europe can overcome these conditions and take part in the "AI Revolution" on its own terms. We want to contribute. Whenever a needed technological layer can be built around or replaced by an independent, Europe-based one, we will put it on our roadmap.

With the right strategy and tools, organizations can tackle the challenges of using AI technologies and keep intellectual property in their own hands. We are developing Alveraign, driven by a deep desire to build a Europe-centric, yet decentral AI platform. At the core, our goal is to deliver an efficient, flexible, and solid foundation for AI use cases that is used by a variety of profit-oriented as well as nonprofit-organizations.

What Alveraign is

A flexible framework for agentic AI — built around how organizations actually work, rather than around what a generic chatbot can do.

Alveraign delivers flexible, agentic AI workflows — accessible through chat and API, built on a multi-tier "cognitive" memory structure. Users build their own scenarios on top of the platform. They decide whether they want a 1:1 chat with an agent, pre-defined squads of agents, or ad-hoc groups assembled for a specific task.

Organizational knowledge sources — such as manuals, SOPs, ongoing correspondence — can be included, and new knowledge accumulates day by day from actual use. Relevant information carriers — such as important partner organizations, competitors (say, "Acme Inc."), or customer types (say, "Security Seeker") — are implemented as digital twins. Agents can embody these personas on demand, so users gain specific insights from the simulation.

Product owners or administrators calibrate the Alveraign AI system by setting one specific system prompt and a multitude of individual roles, goals, stories and tools for each agent or predefined entity.

Large language models (LLMs) can be used "out of the box," but also highly individually configured — as standard or fallback model for each agent.

Where we are, honestly

We think the honest version is more useful than the polished one. Here's where Alveraign stands today.

First things first: The real business project is just about to start. What we have, is a promising technical breakthrough. Today, Alveraign lives on an on-prem system in northern Germany. Two applications are live — a chat interface and an administration dashboard — both reachable through a European identity provider and protected by production-grade authentication. End-to-end login and security boundaries have been verified. Under the hood, the platform uses Europe-aligned components wherever it reasonably can, with a clear plan for replacing the rest over time.

Over the next three months, we're focused on two things: replacing interim authorization with proper role-based access control, and beginning proof-of-concept conversations with early partners. Cloud deployment, multi-tenancy, and on-premise packaging will come later — when a real customer need shapes them, not before.

In other words: Alveraign is not yet a shippable product in the enterprise-catalog sense. It is a working platform, actively developed, with a clear path from where it is today to where it needs to be. If that clarity matters more to you than glossy readiness claims, we're probably having the right conversation.

Live today

Running platform

Chat UI, admin dashboard, production-grade authentication, European identity provider, verified security boundaries, self-hosted on-premises.

Next 3 months

Role-based access & first PoCs

Real RBAC replacing interim authorization. Early proof-of-concept conversations with partners who care about sovereignty and substance. And beyond that: test, test, test — recursively.

Later, when needed

Cloud, multi-tenancy, on-prem installer

Deferred until a real customer commitment makes them necessary. We prefer to shape them around real needs rather than guess.

Technical details (for those who want them)

What Alveraign is built on, today: FastAPI as backend framework, Streamlit for the current UIs, and Llama.cpp (Ollama, Openrouter optional) hosting the Mistral / Mixtral model family (🇫🇷) locally.ZITADEL (🇨🇭) as the self-hosted identity provider, oauth2-proxy with OIDC for per-app session isolation, Cloudflare Tunnel for edge access (under review for EU-native alternatives), PostgreSQL for persistence, Redis for cache and session state (planned switch to Valkey), Chroma as vector store (under evaluation against Qdrant, 🇩🇪),

Two applications are live: app.alveraign.ai (chat) and admin.alveraign.ai (admin dashboard). Session isolation is enforced per application. Current authorization is an email allowlist — an interim security boundary, soon to be replaced by ZITADEL-based RBAC.


A few things worth mentioning specifically:

📡 API access. A FastAPI backend exposes agents and workflows as callable endpoints. Existing business systems — intranet tools, ticket systems, pipelines — can invoke Alveraign agents without needing a chat interface in the loop.

📂 Hotfolder ingestion. A watched-folder pipeline lets organizations plug Alveraign into their existing document flows. Scanned documents, exports from legacy systems, or files dropped by other processes are picked up automatically, classified, and routed — into vector memory for permanent knowledge, temporary working memory for session-scoped context, or a full task queue with locking, success, and error handling for complex workflows like automated archival.

🔁 Agents built in our own orchestrator. Agents work in an explicit "think, act, observe, continue" loop — implemented directly in our own code rather than wrapped through LangChain, CrewAI, or similar third-party agent frameworks. Tools are auto-discovered and isolated, so capabilities can be added or replaced without touching core logic. When a tool fails, the error feeds back into the agent's next step so it can self-correct rather than silently retry or crash.

👁️ Real-time observability. An internal event stream broadcasts every step an agent takes — its reasoning, tool calls, results, errors — in real time. Operators and developers see what's happening while it happens, not just the final output. This also drives the admin dashboard's live view of agent activity and system state.

Who stands behind Alveraign

A real person, at a real address, building something he takes seriously.

Alveraign is being developed and maintained by Ullrich Biedermann from northern Germany. After decades in IT, I keep observing the same recurring pattern: "first open, frontier technology — then creeping dependency on a handful of market-dominating players." Alveraign is my attempt to meet that pattern constructively and creatively.

I believe in solid craftsmanship and honest conversations over polished pitches. If you're curious about what Alveraign can or can't do today, the fastest way to find out is to ask me directly.

Professional domains: Agentic AI Engineering, Technical IT Consulting, Project Management.

Memberships: VGSD (German Association of Founders and Self-Employed Professionals), Consulting Union, Project Management Institute (PMI).

Digital business card: yourvcard.de/u/Oq89rQL5

If this resonates, let's have a conversation.

Not a demo request. Not a pitch. Just a conversation about what you're trying to do and whether Alveraign — today or in a few months — fits.

hello@alveraign.eu