Riven Standards
Riven is a single brand for a family of products. This page is the canonical, always-current reference for how we look, how we run, and what we disclose — brand assets, infrastructure, security posture, subprocessors, model fleet, and release cadence. One source of truth, kept in sync with what is actually deployed.
Brand
The Riven mark is a geometric letterform built from interlocked R and N strokes. Full guidelines live in BRAND.md in rivenai/brand.
Color
Typography
| Role | Family | Weight | Size |
|---|---|---|---|
| Display | Boska | 500 | 72px |
| Hero | Boska | 500 | 48px |
| Section | Boska | 500 | 32px |
| Body | Satoshi | 400 | 16px |
| Code / data | Geist Mono | 400 | 14px |
Display and section headings set in Boska. Body copy, UI labels, and navigation set in Satoshi. Code, tokens, and numeric tables set in Geist Mono.
Logo
Products
Nine products, one brand, one identity layer, one billing system.
The authenticated reasoning workspace — deep thinking, high-context research, and multi-step analysis.
Identity and access for every Riven product, built on BetterAuth with Microsoft Entra ID.
Build, deploy, and automate without leaving the platform — agentic coding and workflow orchestration.
The AI-native media generation surface for video creation, avatar workflows, and production output.
Native macOS / iOS assistant for AI-native browsing built for reach and speed.
Multi-panel intelligence for OSINT, deep research, and geospatial analysis.
Workspace administration — billing, seats, API keys, and usage in one place.
Modular headless commerce infrastructure — catalog, checkout, and fulfillment.
The OpenAI-compatible platform access layer — unified model gateway and routing for developers.
Pricing (v11)
v11 pricing is being rolled out on a parallel branch. See rivenai.io/pricing for the live tier page.
Security & compliance
Data encrypted in transit with TLS 1.3 and at rest with AES-256, across all Riven surfaces.
BetterAuth with Microsoft Entra ID as the workforce identity provider, under the Cassilly Capital tenant.
Production infrastructure runs on Microsoft Azure. Data residency is Azure-backed and configurable per customer requirement.
In progress. Report will be made available through this page once the audit concludes.
Found a security issue? Email [email protected]. We acknowledge reports and do not require a bounty program to take a report seriously.
Subprocessors
The infrastructure and service dependencies behind Riven. This list reflects what is actually in use in production, not an aspirational vendor sheet.
| Subprocessor | Role | Region |
|---|---|---|
| Microsoft Azure | Cloud infrastructure — compute (BigSky-GPU fleet), storage, data residency. | US / configurable |
| Microsoft Entra ID | Identity provider for workforce and customer authentication (Cassilly Capital tenant). | US |
| GitHub (GHCR) | Source control, CI/CD via GitHub Actions, container image registry. | US |
| Cloudflare | DNS, CDN, and edge network in front of public surfaces. | Global |
Infrastructure
Docker Swarm on the BigSky-GPU fleet (Azure).
Traefik as the edge proxy — deployed and managed as dokploy-traefik.
GitHub Actions for build, test, and deploy pipelines.
Container images published to GHCR (GitHub Container Registry).
Model fleet
Riven routes across frontier model providers through a unified gateway. One API key, one billing line, provider-agnostic routing.
Frontier model access routed through the Riven gateway.
Frontier model access routed through the Riven gateway.
Frontier model access routed through the Riven gateway.
Full model catalog with pricing and context windows: docs.rivenai.io/api.
Deploy cadence
Riven ships continuously. Every merge to main builds an image, tags it, and stages it for deploy through GitHub Actions.
Questions on model use, data handling, or this page: [email protected]. Brand and partnership questions: [email protected].