Storage
A company drive and one per program: folder trees, previews, search, multi-select, and share links with password and expiry for the outside world.
The connective tissue is where the record forms.
Chat that doubles as the program timeline. Files with guest-safe links. Permissions that mean what they say. And billing that never surprises you. The unglamorous layer, done properly.
14
permission modules, four actions each
4
gates every request passes on the server
8
features in the platform layer
0
surprises on the invoice
01Team Chat
The channel is the timeline.
Company channels, program channels and DMs: realtime, searchable, with voice notes and file albums. System events post into program chat, so what happened and what was said live in one place.
- Replies, reactions, pins, unread counts, typing: the table stakes, done
- Voice notes recorded and sent in-channel
- @Dispatch answers and proposes actions inside the conversation
- Per-channel AI indexing toggle: you decide what the assistant sees
Four gates, and the button is not one of them.
Hiding a control is decoration. Every request in DMC Pilot passes the same four checks on the server, in order, and each one fails closed, so a hand-typed URL, a stale tab and a copied API call all land exactly where a hidden link does.
- 01
Tenancy isolation
Row-level security in the database. Another organization's rows are not filtered out of your query: they are not reachable by it.
- 02
Module permission
14 modules × view, create, edit, delete, plus special powers like manage billing and external sharing. Checked server-side on the action itself.
- 03
Program scope
Access follows membership. A non-member doesn't get a grayed-out button on a program page: they get a 404.
- 04
Plan feature gate
Plan-gated pages are gated at the route, not just in the navigation, so a URL typed by hand lands in the same place as a hidden link.
The interface is the polite version of these rules, never the enforcement of them.
Storage, permissions and billing, handled properly.
The layer nobody presents in a pitch, and the one every team touches forty times a day.
Roles & permissions
14 modules × view/create/edit/delete, plus special powers. Enforced on the server, on every action: the UI is just the polite version.
Billing & usage
Seats, programs, storage and AI credits visible at all times; overage capped by you or off entirely; invoice PDFs where you'd expect them.
Notifications & digests
Realtime for what needs you now; a daily briefing and digest for what didn't. Frequency is a setting, not a negotiation.
Activity Logs
Every team action, filterable by area and member, searchable, timestamped: with AI-sourced changes labeled as such.
Integrations & API
Flight data, Stripe, Mapbox, R2 and inbound email wired in; a scoped, audited Private API on Enterprise.
Every action, timestamped and attributable.
Activity logs cover every team action, filterable by area and member, and anything an AI proposed carries that label, so the record never blurs who decided what.
Everything in the platform layer
Team ChatChannels, program channels and DMs: where the operational record actually forms.StorageA company drive and a drive per program, with guest-safe share links.Roles & permissionsFourteen permission modules by four actions, plus the special powers, per role.Security & complianceTenant isolation in the database, PII encryption, and GDPR tooling built in.EnterprisePrivate APIScoped API keys with per-key rate limits and an audit trail.Billing & usagePlain billing: what you use, what it costs, and a cap you control.Notifications & digestsRealtime in the product, summarized in your inbox.IntegrationsThe seams that matter, already wired.
Platform questions
Why does chat live inside the product?
Because the operational record forms in conversation. Program channels carry the team's messages and the system's events, a re-optimized transfer, an accepted change request, in one timeline. @Dispatch answers questions in-channel, and channels you opt in feed the Knowledge Base. WhatsApp can't do any of that, and it can't be audited.
How granular are permissions?
Fourteen permission modules: programs, flights, vendors, clients, services, financials, proposals, destinations, storage, waivers, chat, Dispatch AI, team, settings. Each with view, create, edit and delete, plus special powers like manage billing, all programs, and external sharing. Program access is scoped to membership: non-members get a 404, not a grayed-out button.
Can we share files with people outside the company?
Deliberately, yes: a folder or file can be shared on a link with a password and an expiry, and galleries have guest links of their own. External sharing is itself a permission, so who can create those links is up to you.
What integrations exist today?
Live flight data (FlightAware AeroAPI and AviationStack behind one interface), Stripe for billing, Mapbox for places, Cloudflare R2 for file storage, per-program inbound email addresses, and a verified branded sender for outbound mail. Enterprise adds a Private API with scoped, audited keys.
See it on your own programs.
A 30-minute walkthrough with the team, on data that looks like yours. Sales-led onboarding: we load your catalog, your vendors and your first programs with you.