Systems and applications
Capture the core platforms, applications, services, and technology assets involved.
Meridian · Beta
Get architecture clarity before you commit to a direction.
Meridian is an assistant for your architecture work: it captures your context, surfaces the decisions that actually need consensus, and keeps your trade-offs and rationale from getting lost between meetings — so your team can move forward on evidence, not guesswork.
It's in beta — actively refined through real use, not a stripped-down demo. Expect it to keep getting better as more teams put it to work.
Why an assistant
Good architecture judgment is bottlenecked by scattered context, not by talent.
Your systems, constraints, integrations, data concerns, security considerations, and the decisions already made about all of it live in different documents, different people's heads, and different tools — some current, some stale, none connected.
Meridian keeps that context organized, asks the right follow-up questions, and remembers the rationale behind your past decisions — removing that bottleneck whether you're working through it alone or bringing a team along.
What Meridian organizes
A connected view of the architecture context.
Business capabilities
Connect technical architecture to the capabilities and outcomes the business depends on.
Architecture decisions
Preserve decisions with the context, rationale, trade-offs, and constraints behind them.
Integration points
Make dependencies, interfaces, data movement, and cross-system relationships easier to see.
Data concerns
Document data ownership, quality, movement, lifecycle, and reporting considerations.
Security concerns
Identify security, access, compliance, control, and risk alignment considerations early.
How you use it
Bring your context, and keep it as an ongoing assistant.
Meridian isn't a one-time working session — it's meant to stay with you across a project, the way a good assistant would.
- Bring your context: systems, decisions, constraints, open questions — fed in as you have them, not all at once.
- Ask it: use it as a sounding board to surface open decisions, flag risks, and spot gaps before you commit to a direction.
- Keep the record: every decision is kept with its rationale, so nothing gets relitigated or forgotten as people and priorities change.
It's in beta, so expect rough edges — and you can get direct input if you want a second set of eyes on what it surfaces. Open Meridian → · Get in touch →
Tested where it counts
What you get in beta already holds up under real constraints.
Meridian is refined against real consulting and research architecture problems, not designed in the abstract and hoped onto your problems afterward. That means what reaches you in beta has already been tested against actual trade-offs and actual stakeholders — and it keeps changing as that use turns up rough edges, so it gets better under you, not stale.
Origin
Grew out of a real question — and keeps getting tested against real work.
Meridian started with a question worth answering for any team that would rely on it: does making architectural intent explicit actually help hold onto it as AI accelerates delivery? Testing that against real architecture work — across the teams using the beta now — is how the question gets answered, and why Meridian keeps improving instead of shipping once and going stale.