Skip to content
Let ideas be heard and improvements last.
Gemy

Platform core and cross-cutting layers

Every discipline runs on one backbone

My tasks and the approval flow, records, central actions, notifications and reports are the shared backbone of every discipline; the company sets the steps, assignment rules and delegation itself. The AI, integration and trust layers serve every discipline.

  • Flows are tried before publishing
  • Actions close with evidence
  • AI starts switched off
Sample company · demo dataMy work: overdue, this week's and later tasks by due date
My work screen

My work screen

In short

Platform core and cross-cutting layers brings 6 capabilities that are in the product today together on one record, approval and evidence backbone. The company sets the steps, assignment rules and delegation itself; a flow is tried on a sample record before publishing. The AI, integration and trust layers serve every discipline.

  • A flow is tried on a sample record before publishing
  • Actions from every module sit on one list and close with evidence
  • Without a connection, drafts wait on the phone and sensitive records are not written to the device; encrypted storage is switched on by the company
  • AI starts switched off; if enabled, the company picks the service
  • Reports export to Excel and PDF

Three roles, floor to management

The same record moves across three screens; each role sees its own step and the answer to its own question.

Company admin

Builds the organisation, record types, form fields and approval steps in the panel; tries the flow before publishing and picks the short or grouped left menu.

Approver

Sees the approvals, tasks and forms assigned to them on My tasks; gets a reminder before a deadline.

IT

Cloud or self-hosted; read-only API, webhooks, OIDC and SCIM (company enables); encrypted backups and restore drills.

You draw the approval path, the system follows

Step cards, "who does it?" rules, conditions and custom decision buttons. The flow is tried with a sample record before publishing; you see who will be assigned in advance.

  • Assignment rules, fallback rules and delegation
  • A reminder before a deadline
  • "Try it" before publishing
Sample company · demo dataApproval flow editor: steps, assignment rule and condition
Approval flow editor

Capabilities

Capabilities in the core and layers

The cards describe what the product does today; add-on modules are switched on by the company admin. Planned capabilities show only their name, with no description or date.

6 in the product, 3 switched on by the company, 1 on the roadmap

Work and approval

Records opened on the company's own forms and moved through its approval flows.

  • My tasks and approval flow

    In the product

    Approvals, tasks and forms waiting for a person; steps, assignment rules and delegation set up by the company.

  • Records and board

    In the product

    Records opened on the company's record types, each person's records and a board of shared work.

Follow-up

Actions, notifications and reports.

  • Central actions

    In the product

    Actions from every module in one list, with owner, due date and evidence-based closure.

  • Notifications

    In the product

    In-app notifications and email preferences about a person's tasks and records.

  • Reports

    In the product

    Record, action and module reports, with PDF and Excel outputs.

Field

Working where there is no connection.

  • Offline field work

    Company switches on

    Record drafts, photos, action closures and audit answers kept in an encrypted local vault while offline.

    This module is off in a new company; your administrator switches it on from the Features screen.

AI layer

AI assistants that serve every discipline, which the company turns on and chooses a provider for.

  • Institutional memory and AI

    Company switches on

    Permission-aware search, cited answers, weekly summaries and explainable forecasts; the company chooses whether to use AI and which provider.

    This module is off in a new company; your administrator switches it on from the Features screen.

Integration layer

Data exchange with other systems.

  • Integrations

    Company switches on

    Read-only REST API, webhooks, single sign-on, user provisioning and saved Excel / CSV imports.

    This module is off in a new company; your administrator switches it on from the Features screen.

Trust layer

Separation, integrity and protection of company data.

  • Evidence and security

    In the product

    Tenant separation, an append-only change history, a linked evidence chain and a permission matrix.

  • Tenant keys and timestamping

    On the roadmap

Frequently asked questions

Is there a ready-made connector for our ERP?

We don't promise ready-made connectors. With the read-only API, signed outgoing webhooks, an inbound webhook for indicator readings and the registered Excel / CSV bridge (all switched on by the company admin), we work out together what is possible.

Can people sign in with our company account?

Yes. OIDC sign-in with your corporate identity provider and SCIM user sync are switched on by the company admin. Administrators can also use passkeys.

Start with your own record type

Browse the Trust centre or plan a call around your own approval path; we listen to how you work and fit the system to it.

Cookies

Essential cookies are needed for the site to work. Analytics cookies load only if you allow them; declining is as easy as accepting. You can change your choice at any time via the footer link.

Cookie policyPrivacy notice