ASCADI Alternative: Who Reviews Your AI Vendors After Go-Live?
Looking for an ASCADI alternative? The open question is who carries the ongoing §62a review duty once the workshop ends. A factual comparison with sourced claims.
ASCADI, built by Visionary Data, is one of the few AI platforms that takes a German tax firm seriously: a multi-LLM interface spanning GPT, Claude, Gemini and other models, EU-only data residency with no third-country transfer, ISO 27001-certified German data centers, and a set of named assistants shaped around tax practice, from an StBVV fee calculator through a VAT navigator to an audit copilot (https://visionarydata.de/ki-steuerberater, read 2026-08-22). If you are shopping for an ASCADI alternative, a missing feature is rarely the reason.
A different question stays open, and no pricing page answers it: who carries the review duty ASCADI itself describes — permanently, after go-live, every time a new model joins the router? If the honest answer is "nobody here does that on a schedule," what you are missing is not software. It is a different shape. Ours is this: Claude implementation partner — per-client isolated systems, EU or US.
Every ASCADI fact below comes from their own pages; each carries its own read date. Where ASCADI is the better fit, that section is not softened.
Why do firms look for an ASCADI alternative?
Credit first, and here it runs unusually long. ASCADI does not treat professional secrecy as a footnote. The product page commits to a data processing agreement with an explicit confidentiality obligation under §203 (4) of the German Criminal Code (visionarydata.de/ki-steuerberater, read 2026-08-22). A dedicated post on §62a of the German Tax Advisory Act quotes the provision, states plainly that a standard GDPR Article 28 agreement does not contain the required elements on its own, and lists the three written-form requirements: an explicit confidentiality obligation, the instruction on criminal liability under §203, and the instruction on the consequences of a breach (visionarydata.de/blog/62a-stberg-ki-cloud-anbieter, read 2026-08-22). That is careful work. A four-phase onboarding program — workshop, assistant configuration, team enablement, ongoing optimization — sits on top of it.
Three reasons still argue for looking further:
1. The review duty does not end at go-live. ASCADI's own §62a post states the provision requires that suitability "in regelmäßigen Abständen überprüft wird," and names a cadence: an annual re-validation of the contract status and the subcontractor list, which it says suffices in most cases per the BStBK recommendation (https://visionarydata.de/blog/62a-stberg-ki-cloud-anbieter, read 2026-08-22). That is where the text stops. What it does not address: a multi-LLM interface is a subprocessor list that changes. Add another model to the router and you have added a processor — which means running that same assessment again. Who performs it appears on none of the pages we read. In practice it lands on the firm.
2. After enablement, the platform belongs to your team. Maintaining assistants, organizing spaces, modeling new matters — the onboarding is real, but it ends. What comes after needs someone in-house who owns the platform. Without that role, the tool quietly becomes a subscription.
3. No prices on their own pages. Neither the product page nor the tax-firm page carries figures; both route to an initial call (https://visionarydata.de/ascadi, read 2026-08-07; https://visionarydata.de/ki-steuerberater, read 2026-08-22). Numbers exist only third-hand: a vendor-managed profile on OMR lists three tiers from €24 to €50 per user per month, with one-off setup fees of €4,900 and €19,900 attached to the two upper tiers, last edited March 2026 (https://omr.com/en/reviews/product/ascadi-by-visionary-data/pricing, read 2026-08-22). That is an outside source five months old that we could not confirm on ASCADI's own site — do not budget against it without asking them to confirm it.
Five questions this comparison turns on
The yardstick is stated openly so you can redo the math:
- Who carries the ongoing review duty under §62a and §203 — your firm, or the vendor?
- What happens to the confidentiality agreement when another model is added to the platform?
- Are you buying a license with an onboarding program, or a built system somebody operates?
- How many vendors ultimately sit behind your client data, and can that number change without your involvement?
- Is there a public price, or does everything begin with a call?
ASCADI, fairly placed
What they built is not a landing page with AI attached. Domain-shaped assistants across fee calculation, VAT and audit, an onboarding program with named phases, EU hosting without third-country transfer, and no training on customer data by their own account (https://visionarydata.de/ki-steuerberater, read 2026-08-22): this is a serious vertical product. On onboarding duration their pages give two different figures — two to four weeks in one place, roughly two weeks in another. We are not averaging that into a single number. Ask them.
The class it belongs to is "platform with guided onboarding": the onboarding has substance, and afterward maintenance and governance are yours. We worked the monthly math through on meinGPT; what "own schema," single-tenant and multi-tenant actually mean is explained at length in the LocalMind comparison.
Our shape: Claude implementation partner — per-client isolated systems, EU or US
There is no platform license at AILoopwise. The workflows are designed against your own data, built, and then kept running by us. Every client gets its own PostgreSQL schema, whatever the firm's size and with no seat threshold: the storage is separated from the outset. EU clients run on Hetzner servers in Germany; US clients run on US infrastructure. Claude is the primary model; where a processing step must stay inside the EU, it runs on EU-hosted Mistral or on self-operated Ollama. Our founder is certified as a Claude Certified Architect – Professional (Anthropic, issued 2026-08-17), and AILoopwise is a member of the Claude Partner Network.
For the question above, one detail decides it: the vendor list behind your system is fixed and written into the scope. It does not grow in the background. What that means for the review duty is not legal advice, it is arithmetic — a list that cannot change needs reassessing less often than one that can.
On secrecy itself, without inflation: we sign a data processing agreement plus a confidentiality obligation under §203 (4) with the required instruction. That is the same mechanism ASCADI describes on its own product page. We present it here as a baseline both sides meet, not as a distinction.
And the other side of the ledger, unsoftened: there is nothing here to try out — no trial account, and no interface your team could look at this afternoon. There is no published price list. There are no reference clients in tax advisory we could name, and no anonymized ones either: AILoopwise has no paying clients, and we would rather write that down than phrase around it. ASCADI, by contrast, publishes named firms on its own page. If that matters to you, it is a real reason to decide against us.
Where ASCADI is the better choice
Four cases, no footnotes:
- You need an interface your team can log into today. A platform is live faster than a project can be scoped.
- You want references from your own profession before signing. ASCADI publishes them; we have none.
- Model variety under one login matters to you — several providers to choose from, switchable in operation.
- Your firm has someone who will own the platform and would run the annual reassessment anyway. Then the platform shape is the right one.
What to settle before switching
Five steps, plainly:
- Inventory first. Which assistants actually get used? Typically a handful of workflows carry the value and the rest is ballast.
- Keep what carries weight: knowledge bases, documents, and the prompt logic of the assistants people actually use. The effort rarely sits in the prompt; it sits in the context that makes it useful.
- Read the contract: term, notice period, and what becomes of the data once it ends. Only your contract text governs; no blog post substitutes for it, this one included.
- Request the subprocessor list as it stands today — and put beside it the question of who last reassessed it, and when.
- Turn the inventory into a scope. Only at that point does a conversation about size and price mean anything.
ASCADI and AILoopwise side by side
- What you buy — ASCADI: a platform license with an onboarding program. AILoopwise: a system built and operated per client.
- Who administers — ASCADI: your team, after enablement. AILoopwise: we do, on an ongoing basis.
- Models — ASCADI: several providers in one interface. AILoopwise: Claude primary, extended per client with EU-hosted Mistral or Ollama.
- Vendor list — ASCADI: multi-LLM, extendable in operation. AILoopwise: fixed and named in the scope.
- Data separation — ASCADI: EU residency, ISO 27001 data centers (https://visionarydata.de/ki-steuerberater, read 2026-08-22). AILoopwise: additionally a dedicated PostgreSQL schema per client.
- Pricing shape — ASCADI: nothing stated on their own pages; a third-party figure from March 2026. AILoopwise: project price plus a monthly service, disclosed in the scope.
- References — ASCADI: named firms. AILoopwise: none.
Verdict: who owns the review duty from month four?
Within the field of AI for tax firms, ASCADI is a carefully built product with a level of care around professional secrecy you rarely see. If you want a platform and can operate one, you will not go far wrong there. A genuine ASCADI alternative usually turns on shape rather than feature set. With a Claude implementation partner — per-client isolated systems, EU or US, the vendor list is fixed and operations stay with whoever built the system.
Which case your firm actually has takes about half an hour to establish in a call. If the answer is "stay with ASCADI," we will tell you so.
Frequently asked questions
Does a data processing agreement with an AI vendor also cover §62a, or only GDPR?
Not automatically. ASCADI's own post on the subject puts it clearly: a standard Article 28 agreement does not contain the additional required elements by itself — among them an explicit confidentiality obligation and the instruction on criminal liability (visionarydata.de/blog/62a-stberg-ki-cloud-anbieter, read 2026-08-22). Ask any vendor to show you both in writing, ourselves included.
Who checks whether a newly added model still falls under the same agreement?
That is the question this comparison is built around. On a multi-model platform the subprocessor list changes during operation, so whoever triggers the reassessment should be named before you sign. With us the list is fixed in the scope, and changing it is a process with a responsible person attached, not a side effect of a product update.
Why does ASCADI publish no prices on its own pages?
The pages do not explain it; they route to an initial call. Figures exist publicly only in a vendor-managed third-party profile from March 2026 (https://omr.com/en/reviews/product/ascadi-by-visionary-data/pricing, read 2026-08-22), which we could not confirm on visionarydata.de. Treat it as an indication, not an offer. We do not publish a price list either — with us the scope determines the price.
Does AILoopwise have reference clients in tax advisory?
No. AILoopwise has no paying clients, so there are no case studies, no references, and no anonymized hints at any. What we can show is architecture and method — and whether both fit your case is faster to establish in a conversation than through a wall of logos.
Is a multi-model platform inherently riskier than a fixed setup?
No, and that is not the argument here. Multiple models bring real advantages, including fallback options and pricing pressure. The point is organizational: every extension touches the processor list a firm has to keep track of under §62a regardless. If that work is planned for, the variety is a benefit you can use without hesitation.
We already signed ASCADI's data processing agreement. Does it carry over if we switch?
No. Such an agreement binds the parties who signed it, so a change of vendor means a new one, including the confidentiality obligation and the required instruction. The groundwork is not wasted, though: a firm that has already checked those three elements once knows exactly what to look for in the next contract. With the existing agreement, also settle what happens to your data after it ends.
Further reading: