Start on the product, not the plumbing.

Organizations, catalogs, forms, calendars and event-driven workflows, already wired together in Nuxt and Postgres.

Domain event

{
  "name": "customer.created",
  "organizationId": "org_7c1a",
  "entity": { "type": "customer", "id": "cus_4f2b" },
  "actor": { "type": "user", "id": "usr_91e0" },
  "source": "api:customer.create"
}

Every transition emits the same envelope, and a workflow can subscribe to it.

From the trigger catalog

customer.createdproduct.stock_changedform.submission_createdcalendar_event.createdorganization.invitation_createdworkflow.published

Everything your product needs, already connected

Modules that share one event bus, one audit trail and one role system.

Event-driven workflows

Subscribe a workflow to a domain event and the queue runs it, with retries and a log of every run.

A workflow on

customer.created Send Email Wait Send Notification

Organizations and roles

Owners, admins and members in one organization. Invitations expire after seven days.

Products and inventory

Variants, serial numbers, stock movements and photos, with prices in your currency.

Forms and submissions

Build a form, publish it, and read the answers in a table or export them to Excel.

Calendar and events

Month, week and day views, with invitations to members or teams and recurring events.

Teams

Group people inside the organization and invite new members straight into a team.

Communications and notifications

Message teams or people. In-app notifications and email, resolved per recipient.

Reusable email templates

A visual editor per organization, rendered with MJML and sent in three languages.

Audit log

Every mutation is recorded with its actor, its target and its result, including the failed ones.

Organization documents

Private files delivered as short-lived download links. Members read, admins write.

Bulk invitations

Upload a CSV and invite the whole list in the background, with per-row retries.

Describe the workflow, get the graph

Tell the assistant what should happen and it builds the workflow with the same nodes and triggers you would pick by hand. You review and apply; it never publishes on its own.

  1. Describe
  2. Generate
  3. Review
  4. Apply

From clone to first automation

  1. 01

    Deploy

    Postgres, a Nitro server and a queue. Run the migrations and you are up.

  2. 02

    Invite the team

    Create an organization and add people by role, one at a time or from a file.

  3. 03

    Automate

    Pick a trigger, add the steps, and the workflow runs on its own events.

Access is by invitation

There is no public sign-up. Your organization invites you, you sign in, and your role decides what you see.

  • Sign in with a magic link from the invitation email.

  • One account for every organization you join.

  • Your role decides what you can see and do.

Ready when you are.

Sign in to open your organization. New members join through an invitation.