Aliasport console
Manage identities, credentials, mail metadata and audit records.
Open IdentityPrivate developer preview
A working foundation.
Not an open launch.
The product APIs and operator console are implemented. Public signup is not available. These pages explain the project; they are not a promise of production readiness.
Current scope
What exists.
What is still ahead.
- Implemented
- Identity and credential APIs, email extraction, audit records, a source registry and a shared operator console.
- Deployed
- A public website and private operator services on Cloudflare. Access is provisioned separately. This is not a live status page or an uptime guarantee.
- Planned
- Direct borz secret-filling integration. Do not treat the browser handoff as a shipped integration.
- Not available
- Public signup, self-service onboarding and paid plans. No waitlist or launch date is announced.
Operator entrance
Already have access?
The console is for authorized operators. These links do not grant access or create an account.
Before you enter
A few practical answers.
Can I sign up or request an account here?
No. Public registration is not implemented. Existing operators use access provisioned outside this website.
Why did the console deny access or fail to load?
The endpoint may require authorization or may be unavailable. If you already work with the project, contact the operator who provisioned your access. Do not send passwords, tokens or verification codes.
Does trying the demo create an identity?
No. The public passport and lifecycle are local illustrations. They never request a real credential, create an account or call a product API.
Are Aliasport and Signalport the same database?
No. They share a product family and operator interface, but retain separate storage and access boundaries.