Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| customer-portal:start [05.11.2026 09:57] – Create Customer Portal concept: accounts, credits and cross-project license management aria | customer-portal:start [05.11.2026 10:04] (current) – Remove obsolete Customer Portal page; current page is /portal aria | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ~~NOTOC~~ | ||
| - | |||
| - | <WRAP centeralign> | ||
| - | ====== Customer Portal ====== | ||
| - | |||
| - | **Your services, licenses and credits in one place.** | ||
| - | |||
| - | A planned web portal for users and administrators of the Stratum projects. | ||
| - | |||
| - | <badge info> | ||
| - | </ | ||
| - | |||
| - | <WRAP center round important 80%> | ||
| - | **Customer Portal is in the design stage.** This page describes the planned system, not an available service. Registration, | ||
| - | </ | ||
| - | |||
| - | ===== Overview ===== | ||
| - | |||
| - | Customer Portal is intended to bring accounts, service credits and project licenses into one web interface. Users will have a private overview of their own services and licenses; administrators will have a central view of the accounts and licenses they manage across the Stratum projects. | ||
| - | |||
| - | The first version is planned around user accounts, administrator-assigned credits and license records. Connections to individual projects will be added step by step. | ||
| - | |||
| - | ===== Two views, one portal ===== | ||
| - | |||
| - | <grid cols=" | ||
| - | <col> | ||
| - | <card header=" | ||
| - | * Create an account and sign in. | ||
| - | * See available service credits and a history of allocations and use. | ||
| - | * Review your own licenses, enabled features, linked computers and expiry dates. | ||
| - | * Find the services available to your account and follow their status. | ||
| - | * Manage your profile and account security. | ||
| - | </ | ||
| - | </ | ||
| - | <col> | ||
| - | <card header=" | ||
| - | * Review users, account status and assigned roles. | ||
| - | * Allocate service credits with a recorded reason. | ||
| - | * Manage license records, their owners, linked computers, features and validity. | ||
| - | * Track upcoming expirations and review service usage. | ||
| - | * Inspect an audit history of credit and license changes. | ||
| - | </ | ||
| - | </ | ||
| - | </ | ||
| - | |||
| - | ===== Licenses across projects ===== | ||
| - | |||
| - | The portal is planned as a central management layer for licenses, starting with [[stratum: | ||
| - | |||
| - | For Stratum, the planned integration will associate license requests and hardware identifiers with the correct account, show enabled features and validity, and support the issuing and renewal workflow. The existing signed-license mechanism remains the basis of license verification on the computer. | ||
| - | |||
| - | ^ Project ^ Planned connection ^ | ||
| - | | [[stratum: | ||
| - | | [[support: | ||
| - | | [[trade-term: | ||
| - | | Other projects | Additional services connected through a shared API as they become available. | | ||
| - | |||
| - | ===== Service credits ===== | ||
| - | |||
| - | The initial design allows an administrator to assign credits to a user account. The user will see their balance, allocations and consumption, | ||
| - | |||
| - | Connected services will be able to reserve credits, confirm consumption when a service is delivered, or release a reservation when it is cancelled. Credits are planned as internal account balances; the initial version does not include user-to-user transfers or cash withdrawals. Service pricing and usage rules are still being defined. | ||
| - | |||
| - | ===== Web interface ===== | ||
| - | |||
| - | The interface is planned in the style of [[vm-reactor: | ||
| - | |||
| - | ^ User navigation ^ Administrator navigation ^ | ||
| - | | Overview | Overview | | ||
| - | | Services | Users | | ||
| - | | Credits and history | Credit allocations and history | | ||
| - | | My licenses | Licenses across projects | | ||
| - | | Account and security | Audit log and settings | | ||
| - | |||
| - | ===== Planned implementation ===== | ||
| - | |||
| - | * **Go** backend with a web interface and an API for connected projects. | ||
| - | * **SQLite** database for accounts, license records, credit transactions and the audit history; no separate database server for the initial deployment. | ||
| - | * **Transactional credit accounting** with protection against duplicate consumption and concurrent spending. | ||
| - | * **Role-based access**, protected sessions and server-side checks on every account and license operation. | ||
| - | * **Database migrations and backups** as part of operating the service. | ||
| - | |||
| - | ===== Development roadmap ===== | ||
| - | |||
| - | - **Accounts and credits** — registration, | ||
| - | - **License management** — account ownership, linked computers, features, expiry tracking and integration with Stratum' | ||
| - | - **Service integrations** — connect remote support and other projects through the API; add credit reservation and consumption. | ||
| - | - **Payment integrations** — a later phase may add cryptocurrency payments and credit top-ups, with clear payment records, applicable terms and the required legal and operational arrangements. Assets, networks and providers have not been selected. | ||
| - | |||
| - | There is no public release date or installation package announced yet. This page will be updated as the design and implementation progress. | ||
| - | |||
| - | <WRAP centeralign> | ||
| - | <button primary url=" | ||
| - | </ | ||