Opaline Labs, Inc.
Opaline provides team-wide, message-level analytics for Claude Code and Codex coding-agent sessions. It helps engineering teams see session transcripts, token and model usage, costs, activity, recurring blockers and workflow patterns so they can learn how their teams work with coding agents.
At a Glance
- Business and professional engineering organizations
- Software development teams using AI coding agents
- Teams operating across multiple repositories, models and coding-agent sessions
- Security-conscious enterprises requiring controlled deployment and identity administration
AI Tools by Opaline Labs, Inc.
(1)
Opaline
AI Coding Agent Observability
Discussions
No discussions yet
Be the first to start a discussion about Opaline Labs, Inc.
Latest News
Opaline's third Product Hunt launch: team-wide, message-level analytics for Claude Code and Codex, described as PostHog for team coding-agent sessions.
Opaline CLI documentation and repository were refreshed to introduce Opaline as the product and describe the former Rudel project, including the one-command npx onboarding flow.
The public repository recorded opaline-cli 0.10.0 and 0.9.0 releases.
The CLI switched to Opaline as the primary install command and launched guided browser onboarding with live progress.
Products & Services
A hosted website, application and API for uploading, storing, reviewing and analyzing coding-agent sessions, with organization dashboards, message-level analytics, session replay and reporting.
Open-source MIT-licensed Node.js CLI distributed through npx or npm. It discovers local Claude Code and Codex sessions, lets users select repositories, installs agent hooks and automatically uploads selected sessions to an Opaline workspace.
Market Position
Opaline positions itself as a team-wide, message-level analytics layer for Claude Code and Codex, analogous to PostHog for coding-agent sessions. Its Product Hunt description contrasts it with ccusage and Claude Code /insights, which it characterizes as single-user, single-model and relatively shallow; Opaline differentiates through shared cross-repository history, session replay, team comparisons, model/cost context and enterprise controls.
Leadership
Founders
Evren
Public profiles identify him as Evren (GitHub handle evrendom), a designer and builder and the builder of Opaline. He says Opaline was first built for his own team at Obsession DB (YC F26) as a side project called Rudel before being developed as Opaline.
Executive Team
Evren
Founder and builder
Identifies publicly as a designer and builder; he is the Product Hunt maker and GitHub maintainer associated with Opaline.
Founding Story
Opaline began inside the Obsession DB team as Rudel, because the team was using Claude Code and Codex extensively but could not see how teammates were working. Existing tools were described as single-user, single-model and shallow, showing token and cost totals without shared historical context. The initial vision was a shared place to see, replay and learn from coding-agent sessions across repositories and models.
Business Model
Revenue Model
Subscription SaaS priced per workspace member per month, with monthly or annual billing; Enterprise also has a platform fee and custom commercial terms. The open-source CLI is a free MIT-licensed distribution channel for the hosted service.
Pricing Tiers
Up to 3 workspace members and 50,000 agent runs per workspace per month; includes organization-level analytics and the deep session trace viewer.
Billed yearly; unlimited members and agent runs, with organization-level analytics and the deep session trace viewer.
Billed yearly; adds Advanced Session Intelligence and weekly agent reports to the Basic capabilities.
Includes self-hosted/on-prem deployment, invoice or PO billing, SAML/SCIM, granular admin controls, advanced session data modeling, migration/onboarding support, account management and 24/7 founder support.
Target Markets
- Business and professional engineering organizations
- Software development teams using AI coding agents
- Teams operating across multiple repositories, models and coding-agent sessions
- Security-conscious enterprises requiring controlled deployment and identity administration
- Engineering teams adopting Claude Code and Codex
- Understanding coding-agent adoption and usage across repositories and team members
- Tracking API spend, tokens, models, time and session activity
- Reviewing and replaying sessions to learn from effective workflows or diagnose blockers
- Improving agent prompts, skills and team workflows over time
- Security-conscious teams requiring self-hosted deployment or selective repository uploads