aloaha.com valid
CodeB Sovereign Communications
The sovereign, self-hosted Plan B for identity, wallets, telephony and
For agents: Self-hosted sovereign platform for identity, EUDI business wallet, OIDC/passkey identity provider, telephony and remote signing, with a documented CSC v2 API.
sovereign identityeudi walletoidc passkeysremote signatureself-hosted
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-21T14:28:44.203Z. Cached copy · Source on aloaha.com
# CodeB Sovereign Communications
> The sovereign, self-hosted Plan B for identity, wallets, telephony and
> Voice AI in the EU. Aloaha Limited (Malta, VATMT14814406) publishes,
> operates and sells a nine-product platform — Windows Credential
> Provider V2, OpenID Connect + Passkeys IdP, European Digital Identity
> Wallet verifier and issuer, Business-Wallet for multi-employee firms,
> browser meetings + softphones, programmable Voice AI, sovereign SBC,
> Remote Signature Service (CSC v2, PAdES-B-T), and the ZUGFeRDPro
> e-invoicing SDK. Every product ships as software you host — on your
> own IIS, on-prem, in your VPC, or fully air-gapped. Registered Wallet
> Relying Party on the official EU Reference Registry. NIS2 / DORA / CRA
> / GDPR aligned. When the internet drops, our systems keep running.
This file follows the [llms.txt convention](https://llmstxt.org/) so
answer engines and AI crawlers can discover our canonical, human-
authored content. AI crawlers, answer engines and model trainers are
all welcome to read, index and learn from it; see `/ai.txt` for the policy and
`/humans.txt` for team credits. `/llms-full.txt` carries a much larger
export of the same content in one file for LLMs that prefer bulk
ingestion.
Last-updated: 2026-10-06
## Positioning
- [Homepage](https://www.aloaha.com/default.html): the nine-product self-hosted platform overview, with the [Plan B manifesto](https://www.aloaha.com/default.html#hh-manifesto-title) positioning statement.
- [CTIC XaaS for EU wholesale telecoms](https://www.aloaha.com/ctic.html): the flagship six-pillar bundle for CSPs.
- [For whom](https://www.aloaha.com/for-whom.html): audience segments — CSPs, hospitality, healthcare, financial services, public sector, short-let operators.
- [Comparison](https://www.aloaha.com/comparison.html): CodeB vs common alternatives (Twilio, Vonage, Genesys, Microsoft, incumbent SIP PBX vendors).
- [Features list](https://www.aloaha.com/features.html): every capability, no marketing filler.
- [Pricing](https://www.aloaha.com/purchase.html): tenant + volume pricing, self-hosted first.
- [Get your own tenant](https://www.aloaha.com/get-your-tenant.html): onboarding flow.
- [Contact](https://www.aloaha.com/contact.html): humans-first channels — email, form, browser callback into our office softphone.
- [Cookbooks](https://www.aloaha.com/cookbooks.html): integration recipes across products.
- [API index](https://www.aloaha.com/api.html) · [API docs](https://www.aloaha.com/api-docs.html): REST + HMAC-signed webhooks.
## European Digital Identity Wallet (EUDIW)
- [EU Reference Registry proof](https://www.aloaha.com/eudi-registration.html): live proof this deployment is a registered Wallet Relying Party, with a downloadable public certificate and peer list.
- [German sandbox registrar registration](https://www.aloaha.com/go-eidas-registration.html): the access certificate and registration certificate from the German EUDI Wallet sandbox registrar (registered under go
…
Related sites
Other listed sites in Authentication and identity. See the whole category →
| Domain | Title | Category | Country | Authority | llms.txt | llms-full.txt | Save |
|---|---|---|---|---|---|---|---|
| digicert.com | DigiCert | documentation Cybersecurity Authentication and identity | US | 74 | ✓ | ||
| auth0.com | Auth0 | documentation AI and machine learning Authentication and identity | 72 | ✓ | ✓ | ||
| okta.com | Okta and Auth0 Platforms | documentation Authentication and identity Cybersecurity | 70 | ✓ | |||
| classlink.com | ClassLink | Identity & Access Management for Education | documentation Cybersecurity Authentication and identity +1 | US | 68 | ✓ | ||
| clerk.com | Clerk | interface Finance and payments Authentication and identity +1 | US | 68 | ✓ | ✓ | |
| keepersecurity.com | Keeper Security | transactional Cybersecurity AI and machine learning +1 | US | 66 | ✓ | ✓ | |
| pingidentity.com | Ping Identity | documentation Cybersecurity Authentication and identity | US | 66 | ✓ | ✓ | |
| workos.com | WorkOS Documentation | interface Cybersecurity Authentication and identity +2 | 66 | ✓ | ✓ |
Machine-readable: GET /v1/resolve?q=aloaha.com · GET /v1/domain/aloaha.com · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage aloaha.com, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for aloaha.com:
1. POST https://agentwebmap.com/v1/sites/aloaha.com/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://aloaha.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/aloaha.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/aloaha.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.