cmykcloud

How it fits together

One sign-in, every app

Each app is its own OIDC client of accounts. Signing in once gives you every app you have access to, and signing out ends the session everywhere.

Apps that fail independently

Every app owns its own database and deploys on its own. One app being down, or mid-migration, does not take the others with it.

One permission model

Roles and permissions are decided by one policy engine shared by every app, so access means the same thing in all of them rather than being re-invented per app.

A record of what changed

Apps publish what they change to a shared, tamper-evident audit log, so who did what — and when — is answerable after the fact.

• accountsavailable

  One sign-in for every app, your profile, and the apps and OAuth clients admin.

• orgsavailable

  Organisations, members, roles, branch and department structure, and join links.

• notifieravailable

  Email, SMS and voice campaigns, with per-org balances and an itemised ledger.

• auditavailable

  The ecosystem-wide, tamper-evident record of who changed what, and when.

• storageavailable

  Files for an org or a person, with quotas that warn before they block uploads.

• peopleavailable

  Everyone an organisation tracks — staff and external contacts alike.

• formsavailable

  Forms and responses, each form public, authenticated or members-only.

• calendaravailable

  Shared calendars, events, holidays and working days — with attendees and .ics import/export.