Skip to content

For everyday team information

Keep what your team knows in one place.

Mandrel is a workspace of shared forms and lists for the things your team tracks—built so you decide who can view or change each part. Your admins can turn on AI that works with that same information when you want extra help, not a separate mystery tool.

Straight talk: Mandrel is built for teams that outgrew shared files but still need everyday speed—including people who want thoughtful AI on top of real data, not a chatbot floating above a mystery file share.

What you get, in plain terms

Solid structure first—then assistants and automations that shave time off working with that structure. Less tab-switching, less re-reading the same policy paragraph.

Shape

Collections that match real life

Define the fields you need, validate input, link records when one thing points to another, and keep parent/child structure when the world is hierarchical.

Forms

Intake that does not drift

Lay out sections so long workflows stay scannable. People fill the same shape every time—less cleanup for everyone downstream.

Permissions

Who can touch what—on purpose

Grant view, create, update, or delete access per collection so partners and staff see their slice of the work, not the whole attic.

History

A paper trail without the paper

Search and sort long lists of records, and let administrators review activity when you need to show who changed what.

Automations

Reactions when you enable them

When your organization switches on automation, record events can kick off scripted follow-through—less copy-paste, with execution history for transparency.

AI

Help woven into the data layer

Mandrel is deliberate about AI: we build assistant experiences meant to ease searching, summarizing, and next-step work on the records you already trust—within org context, usage limits, and your admins’ go-ahead. Still drafts for anything consequential.

How it works

Three steps—from structure to smarter downstream work once AI and automations fit your org.

  1. 1

    Model your world once

    Set up collections and forms so “the right fields” are always there. References and hierarchy stay consistent instead of re-invented per project.

  2. 2

    Invite people with the right keys

    Match access to real roles: who can read, who can edit, who should stay out. Audits help when someone asks what happened Tuesday.

  3. 3

    Layer on speed with AI and automations

    Use the HTTP API for integrations. When your admins enable them, let automations handle repetitive record work and the assistant answer questions in the context of your collections—less hunting, same source of truth.

Built for different jobs on the same truth

Same workspace—different lenses.

Operators & contributors

Spend time on decisions, not reformatting cells—clear forms, predictable lists, and AI that can nudge you through the next field or recap when you need it (when enabled for your org).

Admins & owners

Onboarding, permissions, audit visibility, and a sane path to turn on AI and automations when the org is ready—without surprise defaults.

Integrators & builders

OpenAPI-backed HTTP surface for the parts you want to script; end users get the same records in the UI with assistants that understand that context when enabled.

Quick answers

Dig deeper anytime in docs or security—not marketing shorthand alone.

Is this a database, a spreadsheet, or something else?
It behaves like a structured workspace: you define types of records (collections), enforce fields and relationships, and let people work through forms. Think “grown-up operational data,” not a blank grid.
How serious is Mandrel about AI?
It is a product pillar, not an afterthought: we integrate assistant capabilities to make everyday interaction with collections and records faster—always respect org boundaries, quotas, and the fact that humans own approvals. Features toggle on only when your organization chooses. Features →
Do you use AI on my data?
Only when you enable that mode. Conversational features may use Google Gemini; retention follows your org policy. The goal is to ease how people work with Mandrel-hosted data, with subprocessors disclosed in the privacy notice. Privacy policy →
Can we integrate with other systems?
Yes. There is a documented HTTP API and reference you can explore without sales theater. API reference →
Are the prices on the site final?
Pricing on the site is illustrative for evaluation. Real numbers should be confirmed with your team and ours before you budget. Pricing →
Where do I report a security issue?
Use the coordinated disclosure path and the security inbox—we want useful reports, not buried tickets. Security & trust →

See whether Mandrel fits the way you work

We are happy to walk through structure, permissions, and how AI fits your data model—honest answers on what ships today and how admins stay in control.