Aleph / operating picture
At a glance
People, Swift-equivalent tokens and commercial activity.
Loading snapshot…
Current Account
activePending Team Requests
0Plan & Membership
planWorking notes
Accounting details 0 completed sales
Allowance figures are Swift-equivalent tokens over each person’s current plan period; pending credits are separate from settled use. Provider token counts are under Users, in Hosted usage, for any period. Sales cover recorded completed purchases.
Demand Ledger
Tenant Directory
Aleph Intelligence API
One row per registered channel. The endpoint is the literal line a developer pastes, and the channel answers as soon as it is created — choosing the workspace is what publishes it.
Create channel issues the endpoint and, for a channel called from the integrator’s own server, its key — together, in one step. Both are derived from the channel, so neither can be made before it. Whatever is in the chosen workspace becomes readable by anyone who can reach that channel.
Signed-in apps
Apps whose users sign in with their own Aleph identity (AAIP P1). A web app returns its users to the exact https address registered here; a desktop app returns to its own machine and registers none. Register app issues the app’s credential once, with the handover message. Registering and revoking an app is the root admin’s act.