Architecture
Plexus Psychiatry
A solution-architecture summary — how the system is designed, and why. Verified from the source code.
- Type of system
- A clinic running on the Baton platform, plus two public sites
- Users
- Patients (researching or ready to book) and clinicians
- Hosting
- United Kingdom
- Main stack
- Baton platform (see Baton) + a Next.js public site
- Status
- Live (opened 2025)
- Built for
- Client — a private psychiatric clinic
The problem
A new clinic needs two things that pull in different directions: a public presence that earns trust, and a system to actually run on. Patients also arrive in two frames of mind — some still making sense of their symptoms, some ready to book — and one page rarely serves both well.
How it fits together
Users
Patients (researching or ready) · clinicians
Front end
plexuspsychiatry.com (Baton patient app) + adhd-autism.net
Tenant boundary
Backend / API
Baton clinical platform (see the Baton architecture)
Database
PostgreSQL (via Baton)
Plexus is the first clinic (tenant) on Baton.
External services
- Anthropic Claude
- Stripe
- Microsoft Teams
- Mailjet
- NHS lookups
Tech stack
Public sites
- plexuspsychiatry.com — the Baton patient app (Next.js)
- adhd-autism.net — a separate education site
Clinical platform
- Runs entirely on Baton — see the Baton architecture for backend, database and services
Hosting
- United Kingdom
Key design decisions
Two public sites, one funnel
Why: A symptom-searcher and a ready-to-book patient need different pages. adhd-autism.net educates and earns trust; plexuspsychiatry.com converts.
Trade-off: Two public front ends to maintain instead of one.
Run on Baton rather than off-the-shelf practice software
Why: One record from booking to discharge, built for exactly this kind of clinic, from one supplier.
Trade-off: A custom platform to own — addressed by Baton being multi-tenant and reused.
Open the clinic on a platform, not a project
Why: Building Plexus on Baton means the clinical system was production-grade from day one and improves as the platform does.
Trade-off: More engineering up front than a single-clinic tool.
Security & data protection
- The clinical system is Baton — its security applies here in full: UK-hosted, role-based access enforced on the server, staff two-factor, a complete audit trail, and no self-registration.
- See the Baton architecture for the detail.
Built to hold up
- Performance
- Public sites are lightweight; the clinical app is the Baton patient app (server-rendered).
- Availability
- Runs on the Baton platform's UK hosting.
- Scalability
- As a Baton tenant, Plexus scales with the platform.
What we'd do next
- Add a Content-Security-Policy to the public sites.
- See the Baton architecture for the platform-level roadmap.