MITHRION.DEV

MITHRION.DEV

Run client work from one operating workspace.

For consultants, studios and small delivery teams: projects, tasks, CRM, calendar, documents and reports in one workspace — nothing rebuilt, re-synced or lost between tools.

Create your workspaceSee the modules

Ten modules, live today. Self-serve — no demo call.

The operating layer

One system that holds the work and the context around it.

Change a project and the calendar, the report and the client record already know — because they are one system, not five that sync.

MITHRION
Command CenterKnowledgeProjectsActivityTasksTeam & PermissionsCRMReportsCalendarDocumentsClerkAuthStripeBillingGitHubSource · CIVercelHostingPostgreSQLData

Owned by MITHRION

Command Center · Projects · Tasks · CRM · Calendar · Documents · Reports · Team & Permissions · Activity · Knowledge — plus Automations and Intelligence, in development.

Connected services

Clerk · Stripe · Vercel · PostgreSQL · GitHub. The workspace owns the operating layer; these run underneath it.

Modules

Explore the platform, module by module.

app / projects
Projects6 active · 2 at risk
Migration projectDeliveryOn track
Quarterly retainerRetainerAt risk
Client onboardingFixed scopeOn track
Available nowCommand Center

One dashboard for what is urgent, overdue, blocked, assigned, and recently changed.

Available nowTeam & Permissions

Invitations and role-based access for teams beyond a single workspace owner.

Available nowActivity

A read-only, workspace-scoped feed of what changed — every update, in one place.

Available nowKnowledge

A read-only, published home for the decisions and context your team relies on.

Coming nextAutomations

A small, auditable trigger-condition-action engine for the operational work that repeats.

Coming nextMITHRION Intelligence

A governed AI layer that cites real workspace data — never invents or changes it.

How the system works

The interface changes by module. The operating model underneath does not.

  1. 01

    Capture

    Work goes in where it happens — no import ritual.

  2. 02

    Connect

    A task belongs to a project, a project to a client. Context is a relationship.

  3. 03

    Operate

    The Command Center surfaces what needs attention; roles decide who can change it.

  4. 04

    Report

    The weekly status report is generated from the same data — nothing re-entered.

Why it's credible

Built like production software, not a concept.

A running application with a Postgres data model and a real release process.

  • Real dataActor and workspace resolved server-side. Cross-tenant access is a tested failure case.
  • Real workflowsProjects, tasks, CRM, calendar and documents — shipped and usable now.
  • Real permissionsOWNER / ADMIN / MEMBER write, VIEWER reads. Admin authority bound to an immutable identity.
  • Real operationsReviewed migrations. Recoverable delete, versioned export, durable removal.

Evidence

Recorded passing tests (Shift Manager)
298
Every change scanned in CI
CodeQL + audit
Accessibility
axe, per route
Deploy verification
/deployment.json + smoke

See the work →Honesty commitments →

Straight answers

The questions that decide whether this is for you.

Is this available now, or am I joining a waitlist?

Ten modules are live today. You create a workspace and use them — self-serve, with no demo call in the way.

Who can see and change what?

OWNER, ADMIN and MEMBER can write; VIEWER reads. The actor and the workspace are resolved server-side on every request, and cross-tenant access is a tested failure case rather than an assumption. Admin authority is bound to an immutable identity.

What runs underneath it?

Clerk for authentication, Stripe for billing, Vercel for hosting, PostgreSQL for data, and GitHub for source and CI. The workspace owns the operating layer; those services run underneath it.

Can I get my data back out?

Yes. Deletes are recoverable, exports are versioned, and removal is durable when you do mean it permanently. Migrations are reviewed before they run.

How do I know it actually works?

Every change is scanned in CI with CodeQL and a dependency audit, accessibility is checked per route with axe, and each deploy is verified against /deployment.json plus a smoke run. The shipped client system carries 298 recorded passing tests.

Open the workspace, or bring us the problem it should solve.

Self-serve — create a workspace and use the modules now, or bring the operation you need built around it.

Create your workspacePrepare a project brief
drag the letters