Narrative
Less dashboard.More product thesis.
The old page read like an internal status board. The new page leads with positioning, shows proof earlier, and uses mock product structure to imply capability instead of listing features in the abstract.
riften.aiLogisticsSingle-tenant runtime
Branded AI workspaces,without exposing the machinery.
Riften gives Maspeth Freight Ops a sharp client-facing surface for chat, intake, and workflows while the agents, integrations, and operator logic stay behind the product where they belong.
Pending
0
Requests currently waiting on review or automation.
Completed
0
Tenant actions closed in the current week.
Hours
0
Operator time already reclaimed through the workflow layer.
Tenant preview
Maspeth Freight Ops
Logistics lane
Inbox
Route intake from Gmail and shared inboxes
Summarize next action for operators
Keep the client inside one branded host
Runtime state
Queue
0
Integrations
Gmail, Drive, CRM, webhooks
Client request
Need a clear summary of the next action, the source inbox, and which operator should own it.
Riften response
Source data stays tenant-scoped, the workspace stays branded, and the operator gets a concrete next step instead of raw model output.
Host
riften.ai
Skills
1 active
Database
Configured
Why it reads better
Editorial typography instead of generic SaaS chrome
Product-state panels that imply real workflow depth
Tenant proof woven into the story, not hidden below the fold
Clear sections for platform, outcomes, integrations, and security
Platform
A public-facing product surface with an operator-grade control plane underneath.
The reference you shared works because it feels sharp, quiet, and assured. This version applies that same restraint while keeping Riften’s actual multi-tenant model visible in the details.
01
Branded front door
Every client gets a clean, host-aware workspace.
Maspeth Freight Ops resolves on riften.ai, keeps its own branding, and lands users in the right tenant without exposing internal runtime complexity.
Custom host resolutionTenant-specific brandingOrg alignment through Clerk
02
Operator layer
Humans, automations, and agents work in the same lane.
Dispatch automation and freight-document intake for warehouse and carrier ops.
0 active tasks in queue0 completed this week0 hours recovered
03
Connected systems
Integrations are first-class, not bolted on after launch.
Chat, email, drives, CRM data, and webhook sources feed one control plane so every action can carry context forward.
Unified chat and integrations surfacesTenant-scoped connection stateDatabase ready
Workflow model
Incoming requests land in one tenant lane.
Operators see the same context the client sees.
AI actions stay constrained to that workspace and its connected systems.
Outcomes
Proof should show up before the reader has to trust you.
Instead of generic promises, the page now anchors on tenant-level operating signals that already exist in the app model.
Pending
0
Requests currently waiting on review or automation.
Completed
0
Tenant actions closed in the current week.
Hours
0
Operator time already reclaimed through the workflow layer.
Skills
1
Active workflow skill profiles loaded inside this tenant.
Integrations
Riften meets clients where the work already happens.
The landing page now treats integrations like part of the product story instead of burying them in secondary cards.
Gmail
Slack
Salesforce
Google Drive
Teams
Outlook
HubSpot
SharePoint
Webhooks
Supabase
Gmail
Slack
Salesforce
Google Drive
Teams
Outlook
HubSpot
SharePoint
Webhooks
Supabase
Gmail
Slack
Salesforce
Google Drive
Teams
Outlook
HubSpot
SharePoint
Webhooks
Supabase
Gmail
Slack
Salesforce
Google Drive
Teams
Outlook
HubSpot
SharePoint
Webhooks
Supabase
Security & FAQ
The operating model stays rigorous.
A better landing page should still tell the truth: tenant separation, operator control, and environment readiness are product constraints, not marketing garnish.
Does each client stay inside its own tenant?
Yes. Hosts resolve directly to a tenant context, branding is tenant-scoped, and organization access stays aligned to that workspace.
Can operators stay inside the same product surface as end users?
That is the point of the control plane. Human review, AI actions, and integrations all route through one branded interface instead of separate back-office tooling.
What happens when data systems are not fully configured yet?
This tenant already reports a configured database layer, so the marketing surface can confidently describe a live control plane.
Closing section
Put a real product surface in front of your AI workflows.
Keep the client experience calm. Keep the operators in control. Keep the runtime where it belongs.