Grin Lab
grin lab
Innovation. Not Complicity.

We build opinionated software that automates the work that shouldn't need humans — and surfaces the intelligence that should.

Products

Software that does the work.
Not just assists.

Each Grin Lab product is built around one conviction — the work that matters should be fully automated, not partially delegated to a chatbot.

Private beta
01 / Product
Meridian
Engineering intelligence, automated
Meridian watches your Git, Slack, Jira, and calendar — and tells you what's actually happening in your engineering org. Standups become optional. Status updates become automatic. Opportunities propose themselves.
Signal classification Auto Jira updates Resourcing proposals Customer VPC No standups
Explore Meridian
02 / Product
Coming
soon
The next Grin Lab product is in early design. Details coming soon.
Grin Lab / Meridian
Now in private beta

Engineering intelligence,
automated

Meridian watches your signals — Git, Slack, Jira, calendar — and tells you what's actually happening in your engineering org. No standups required.

80%
fewer standups
24h
to first insight
1-click
manager approval
Signal detected: payments-service BUILD confidence 0.94 Drift flagged: auth-service claimed DONE — no deploy detected Opportunity proposed: API gateway consolidation — $240k ROI Risk detected: DISCUSS loop without DECIDE — 4 days Engineer capacity update: squad-phoenix 73% allocated Q2 Incident resolved: P1 payments outage — 23min MTTR Commitment fulfilled: checkout API migration shipped on schedule Signal detected: payments-service BUILD confidence 0.94 Drift flagged: auth-service claimed DONE — no deploy detected Opportunity proposed: API gateway consolidation — $240k ROI Risk detected: DISCUSS loop without DECIDE — 4 days Engineer capacity update: squad-phoenix 73% allocated Q2 Incident resolved: P1 payments outage — 23min MTTR Commitment fulfilled: checkout API migration shipped on schedule
Three stages.
One continuous loop.
Meridian moves through Observer → Authority → Proposer automatically. Click each stage to see it in action.
meridian / signal-feed — live LIVE
GIT
feat: add retry logic to payment processor
@sarah · payments-service · 2 min ago
BUILD
SLACK
blocked on auth dependency, waiting on team
@james · #payments · 5 min ago
BLOCK
GIT
fix: resolve null pointer in checkout flow
@priya · checkout-api · 8 min ago
FIX
JIRA
deploy auth-service v2.4.1 to staging
@marcus · auth-service · 12 min ago
DEPLOY

Watches what's actually happening

Meridian continuously reads signals from every tool your team uses — Git commits, Slack messages, Jira updates, calendar events — and classifies them into canonical work events in real time.

Real-time classification — 12 intent labels, 9 domain categories, confidence scored per signal
No manual input — engineers keep working as normal. Meridian reads the signals they already generate
Drift detection — when a claim doesn't match evidence, it gets flagged automatically
meridian / manager-approvals
Jira update — payments-service
PENDING
Meridian detected BUILD activity for 3 days with no Jira update. Proposed status change from "In Progress" → "Review Ready"
Confidence94%
Evidence7 commits, 2 PRs merged
Engineer@sarah
Drift detected — auth-service
REVIEW
@james claimed "auth migration complete" in standup but no deploy signal detected in the last 48h
Claim madeTuesday standup
Deploy detectedNone
Risk levelMedium
All caught up
Meridian will surface new approvals as evidence accumulates

Updates your tools, not your team

Meridian writes back to Jira and Confluence automatically based on what it observes. Exceptions surface to the manager as one-click approvals — not status update requests.

Automatic Jira updates — status, assignees, and progress updated from evidence, not self-reporting
One-click approvals — managers approve exceptions, not status updates. Override always available
Engineer profiles — domain expertise, capacity, and velocity tracked from signals — never from self-reported data
meridian / opportunity-proposals
API gateway consolidation
Detected from: Confluence doc by @alex · 6h ago
$240k
Backlog priorityRank #2
Suggested engineers
SL
Sarah L. — payments-service expert
95% match
MP
Marcus P. — infrastructure lead
88% match
JP
James P. — currently blocked
leave conflict

Proposes what to build next

Meridian reads every signal source — sales docs, meeting notes, customer escalations, market signals — and proposes projects ranked against your current backlog, with ROI estimates and resourcing plans.

Any signal source — a salesperson adds a Confluence doc, Meridian detects the opportunity and proposes a project within 24h
ROI-ranked backlog — every proposal is scored against existing commitments and capacity before it reaches you
Smart resourcing — suggested engineers based on domain expertise, current capacity, and leave conflicts
From signals
to decisions
No months-long implementation. No custom scripting. Connect your tools and Meridian starts learning immediately.
01

Connect your tools

Plug in Git, Slack, Jira, Confluence, and Google Calendar. Most integrations configured in minutes. Meridian runs entirely in your VPC — your data never leaves your infrastructure.

02

Vocabulary bootstraps automatically

Meridian scans your existing tools, extracts your component names, team names, and product areas, and builds a vocabulary map of your org. No manual configuration required.

03

Intelligence surfaces to managers

Summaries, risk alerts, and opportunity proposals arrive via Slack and Confluence — the tools you already use. Your engineers keep working exactly as before.

Profiles built from
signals, not self-reports
Meridian builds a living intelligence profile for every engineer — from what they actually do. Click any engineer in the sidebar to explore their profile.
MERIDIAN / engineer signals
OBSERVER ACTIVE WRITE-BACK: ON 7 SIGNALS TODAY
TEAM · PLATFORM
AC
Alice Chen
Senior Engineer
BK
Bob Kumar
Engineer
SR
Sara Reyes
Engineer
DL
Dan Liu
Lead Engineer
MP
Mia Park
Engineer
TEAM · GROWTH
JN
James Ng
Engineer
FS
Fatima Said
Senior Engineer
AC
Alice Chen Senior Engineer · Platform Team profile since Mar 2026 · 47 days of signals
api-gateway auth payments 59% capacity
You are viewing your own profile · All data visible to you
VELOCITY · LAST 30 DAYSvs personal 90-day baseline
PRs Merged
23
↑ +4 vs baseline
Avg Review Cycle
1.2d
↓ faster than baseline 1.8d
Commit Frequency
4.1/d
→ on baseline
Rework Rate
3%
↓ below baseline 6%
OPT-IN
WEEKLY COMMIT ACTIVITYlast 12 weeks
Jan Feb Mar now
DOMAIN EXPERTISErecency-weighted · decays if inactive
api-gateway 0.91
auth 0.84
payments 0.72
rate-limiting 0.68
data-pipeline 0.45
mobile-app 0.22
Active (last 14d) Fading (15–60d) Stale (60d+, decaying)
RECENT SIGNALSinferred from git · slack · calendar
Merged PR #1247 — api-gateway rate limiter refactor
git · 2h ago · 847 lines changed
REFACTOR DONE
conf 0.94
Declared intent in Slack — auth token rotation fix "by EOD"
slack · 5h ago · no code movement yet
FIX PENDING
conf 0.81
Code review on PR #1251 — payments retry logic
git · yesterday · 3 comments, 1 approved
REVIEW
conf 0.89
Attended architecture decision meeting — api-gateway versioning strategy
calendar · yesterday · decision: versioned endpoints approved
DECIDE
conf 0.76
AVAILABILITY · NEXT 6 WEEKS
Available
now – Apr 14
Annual Leave
Apr 15 – Apr 22
Available
Apr 23 →
⚠ Leave conflict detected
Acme Corp proposal start date overlaps. Resourcing engine flagged this.
PROJECT RISK FLAGS
→ Intent without execution
Auth token fix declared 5h ago. No commits detected. Watching.
✓ API refactor closed cleanly
PR merged, no rework signals, velocity stable.
COLLABORATION GRAPH
BK
Bob Kumar
18 PRs
DL
Dan Liu
12 PRs
SR
Sara Reyes
7 PRs
PERFORMANCE SIGNALS
🔒
Organisation opt-in required
Rework rate, PR longevity, and code quality signals are collected but not displayed until your organisation enables this. You will be notified before anything is shared with your manager.
MY DATA
Download my profile Export ↓
Request a correction Submit ↗
View manager audit log View ↗
What Jira can't do.
What Rovo won't do.
Capability Jira + Confluence Atlassian Rovo Meridian
Source of truth What humans typed What Jira contains What actually happened
Contradicts Jira when evidence says so
Proposes new projects from any signal
Produces resourcing plans with capacity data
Surfaces ROI estimates ranked against backlog
Requires humans to update tickets Always Relies on Jira hygiene Never
Runs in your VPC
Connects to your
existing stack
Meridian reads from the tools your team already uses. No new workflow. No new habits.
GitHub
GitLab
Slack
Jira
Confluence
Google Calendar
Google Meet
Zoom
Linear
Notion
PagerDuty
Datadog
Bitbucket
Microsoft Teams
Outlook Calendar
More coming
"We were spending three hours a week in standups gathering status that Meridian now surfaces automatically. Our managers finally have time to do actual management."
JR
Jamie Rodriguez
VP Engineering, Series B fintech

Stop asking what's happening.
Start knowing.

Meridian is in private beta. Join the waitlist and get early access for your engineering team.