Ralti is a spreadsheet-first workspace application. The web client uses Next.js and React. The installed iOS shell renders that same responsive application in a persistent system WebView and adds device integrations; Android currently retains the earlier Flutter interface. These clients use the same Node.js API for authorization, validation, persistence, and background work. The public marketing website is a separate deployment from the authenticated application.

Follow a change from idea to saved record#

  • A client selects a workspace and submits a typed operation or asks for an AI proposal.
  • The API verifies identity, membership, role, request scope, and the expected workspace revision.
  • The domain engine validates the entire operation batch, including references between operations.
  • A database transaction persists the accepted changes, revision, activity, and undo information.
  • Clients receive the updated state; background jobs process eligible events and search indexing.
LayerResponsibility
InterfaceNavigation, editing, review, and presentation
DomainTypes, invariants, operations, and risk
PersistenceTransactions and database boundaries
Background workAI, email, workflows, search, deletion, integrations, and persistent agent members

Ask Ralti stages proposals for human review. Persistent agent members separately execute explicitly delegated, bounded work through the same canonical record, rule, document, email, and integration services. They keep their own identity, source evidence, exact reviews, and effect receipts. An explicitly permitted automatic record change is still attributed to the agent, not to its reviewer.

Treat the checked-in domain types and route handlers as the implementation contract. “Space” and “item” remain internal names for sheets and records in several API payloads; changing the UI label does not rename those wire fields.

Build on the same primitives#

A form is a one-page App. App journeys use the existing Flow engine; public intake, invited access, groups, files, and embeds share release-bound authorization. Document columns reopen a record’s linked document. Auto-number allocations belong to the canonical record mutation, independently of documents. AI authoring produces the same definitions used by manual editors.