Vol. XV · Functory Quarterly№ 001 · Edition 2026
I
Where a build starts

Starter kits.

Tested bundles of records, rules, and workflows that a deployment selects by name.

Every deployment boots on a small baseline, then opts into the kits its product needs. A kit that depends on another says so, and a deployment that selects it without its dependencies is refused at boot, not at first use. Where a kit already fits your domain, the build starts close to day one.

Every deployment gets

Users, sign-in configuration, sessions, transactional email templates, session audit, and the tenant roster.

Selecting kits

FUNCTORY_STARTER_KITS=corp-university,learning,memberships,audit,notifications

An unknown kit, a missing dependency, or two kits claiming the same record type all fail fast at boot.

II
Domain kits

The moving parts of your domain.

Each kit carries the record types, lifecycles, and rules for one area of a product. Select the ones you need; dependencies are declared, not conventions.

reservations

Reservations

Bookable inventory with real-time availability: reservations, bookings, reservable items, waitlists, cancellation policies, and calendars.

SeeReservation System

memberships

Memberships

Groups and communities, with agreements, announcements, and a per-person inbox for every notice they send.

SeeGroups & Teams

marketplace

Marketplace

Two-sided selling: listings, providers, pricing policies, scoring, sellable experiences with dated sessions, and co-hosting with revenue splits.

Ships with a deployment runbook and an escape-hatch guide.

Requiresengagement, commerce

SeeMarketplace

engagement

Engagement

Ratings, reviews, and other interactions, plus event hooks, file sharing, content, messaging including inbound SMS, experiments, imports, catalogs, and public submissions.

Requiresnotifications

SeeEngagement, Interactions

events

Events and ticketing

Events, sessions, and venues, with ticket types, reserved seating, and ticket orders that hold, take payment, and issue in one durable flow.

growth

Growth

Referrals, affiliates, and short links.

SeeReferrals

learning

Learning

Courses and lessons on their own, so a training product does not have to carry everything in engagement.

notifications

Notification preferences

Each person's notification preferences, shared by the kits that send to them.

SeeNotifications

III
Product kits

A whole application, selected by name.

corp-university

Corp University

A whole sellable application rather than a capability: onboarding journeys, versioned SOPs, and compliance training. The Atlas demo and a customer deployment run the same catalog, so what you click through is what you would deploy.

Requireslearning, memberships, audit, notifications

Open Atlas
IV
Platform kits

Cross-cutting, and opt-in.

Capabilities that every product might want, selected rather than inherited, so a deployment carries only what it uses.

  • auditTamper-evident audit log
  • gdprData subject requests
  • webhooksOutbound webhooks
  • feature-flagsRollouts and kill switches
  • collectionsWishlists, favorites, playlists
  • localizationTranslations and locales
  • reference-dataImmutable lookup data
  • cdpCustomer data platform
  • verificationIdentity verification records
  • credentialsSigned credentials, such as certificates
  • eeoEqual-opportunity self-identification
  • ops-alarmsOperational alarm history

Coda

Start from a kit.

Tell us what you are building, and we will tell you which kits already cover it and where custom engineering belongs.

Talk to an engineerRead the docs