Give clients a portal. Keep your team in Linear.

A branded portal for each client - tickets, roadmap, and changelog that sync with Linear in both directions. No copy-pasting updates, no client seats on your real board.

Start freeSee how it works
aster.lucidlane.dev
AAster
New request
AI · analyzing
Similar requests found — join one instead?
AST-214SSO login fails on Safari
AST-209Export report as CSV
None of these — file as new request
RequestStatusVotesUpdated
AST-214SSO login fails on Safari
In progress892h ago
AST-209Export report as CSV
In review45h ago
AST-221Bulk-invite teammates by email
To do271d ago
AST-187Webhook on ticket status change
Backlog616d ago
AST-198Dark mode for dashboards
Done1733d ago

0%

of duplicate requests deflected by AI

0.0h

median first response across portals

0%

of comments synced both ways to Linear

0

client portals run by the average agency

Portals & scoping

One workspace, many client portals - no client ever sees another's data.

Every Linear customer becomes a branded portal automatically. Behind the scenes, a scoping layer decides exactly which projects, labels, and fields each portal can see - and enforces it on every read and write.

  • Portals auto-created from every Linear customer
  • Scoped per-portal to specific projects, labels, and fields
  • Every read and write enforced against that scope - no exceptions
  • Custom subdomain, logo, and accent color per client
Per-portal scopeConfigure
Portal
Projects
Labels
Roadmap
Changelog
Aster
Bluebarrow
Lumen

Every read and write passes the scope — no cross-client leakage, ever.

Two-way sync

Conversations flow both ways, with the right names attached

Client comments post into Linear under a clearly marked client account - never confused for your team. When your team replies in Linear, it shows up in the portal under their real name and photo.

  • Client comments sync into Linear, clearly tagged as external
  • Team replies surface in the portal under real names
  • Status changes and shipped work sync instantly via webhook
Live syncReal-time
A

Aster portal

client-facing

L

Lucidlane

scoping · attribution · SLA

≡

Linear

system of record

AI DEFLECTION

Duplicates die before they are filed

As a customer types, Lucidlane suggests matching help articles and similar tickets. If they file anyway and a confident match exists, an auto-comment links them to the existing request instead of opening a new one.

  • Live suggestions while customers compose
  • Confident matches auto-linked after submit
  • Suggestions pulled only from that client's own tickets

38%

caught early

  • Caught before filing38%
  • Linked after filing12%
  • Filed as new50%

Changelog

Ship in Linear, publish to every portal

Closed issues become polished "what shipped" entries, drafted by AI on your cadence - weekly, monthly, or per sprint. Review, then publish per portal and notify subscribed customers in one click.

  • AI drafts entries from merged Linear issues
  • Edit before it goes out - nothing publishes unseen
  • Set cadence per portal, publish independently
  • One-click notification with unsubscribe
What shipped · Week 29AI drafted
AST-198Dark mode for dashboards
AST-201Faster report generation
AST-205Fixed CSV export encoding
Published to Aster · 47 customers notified

Roadmap

A roadmap clients actually vote on

Configure columns from Linear workflow statuses or labels, then choose what each portal exposes. Votes flow back into the same Linear issues your team already triages.

  • Per-portal visibility over every column and card
  • Votes attach directly to the underlying Linear issue
  • No separate backlog to maintain
Aster roadmapTop voted
Under review2

Slack notifications

API rate limits

Planned2

SSO / SAML

Custom fields

In progress2

CSV export

Dark mode

Inbox & SLA

One inbox. Every client, every portal.

No per-client inboxes to juggle. Every conversation lands in one agency inbox, tagged with a reply state - new, awaiting, answered, closed - and a per-client SLA timer, so no thread goes quiet.

  • One global inbox - filter by portal, not login per client
  • Reply states drive triage across all portals
  • SLA timers flag at-risk threads before they breach
One inbox · every portal3 total
All portalsAsterBluebarrowLumen
JW

Jane · Aster

Any update on the Safari fix? Our launch is…

NewSLA 47m left
PC

Priya · Lumen

Can we get SSO on the Growth plan?

AwaitingSLA 2h 6m left
MR

Marco · Bluebarrow

Loving the new dashboard, nice work!

Answered
  • Agency inbox with reply states
  • SLA tracking per client
  • White-label branding
  • Embeddable widget
  • Cmd-K search, everywhere
  • Custom subdomains per portal

How it works

Live in an afternoon

  1. 01

    Connect Linear

    OAuth in. Lucidlane backfills your customers, projects, and issues, then stays live from webhooks.

  2. 02

    Scope each portal

    Decide what each client sees - projects, labels, priorities - and set their brand, domain, and roadmap columns.

  3. 03

    Publish and breathe

    Clients track requests, vote on the roadmap, and read the changelog. Replies sync straight back into Linear.

The landscape

The angle nobody else covers

Same core bet as every Linear-native portal - Linear stays the system of record - but built for agencies running many client portals, not a single product team.

Capability
Lucidlane
Linear native
Other portals
Linear stays the system of record
Client-facing portal
Many client portals (agency model)
Per-client scoped visibility
Two-way comment sync with attribution
AI deflection of duplicate requests
Per-portal changelog + roadmap voting
White-label + custom subdomains
Embeddable widget

Your clients are already in Linear. Give them the portal.

Connect your workspace and publish your first client portal today. Built for agencies running many clients - not bolted onto a single-team tool.

Start freeSign in

Free during early access Connect Linear in one click