Ship it as your product.
LogClip is sold direct — but if you put software in front of your own customers, the parts they touch can carry your brand instead of ours. Here is exactly what that covers today, and what it does not.
I clicked “Pay now” four or five times and nothing happened. Card was never charged.
Three products, one embed — the same markup in all three, and the same session: sess_8f21c4 at 0:41 / 3:18, the rage-click on the checkout button that never fired. An ecommerce agency's support desk. Light, tight corners, their green.
The player, embedded in your product
Mount session replay inside your own support console, admin panel or customer dashboard with one script tag or one React component. It renders as part of your interface, not in a frame that belongs to us.
Themed to your brand tokens
Every embedded surface reads its colour, radius and type from CSS custom properties you override. Pass your own palette and the widget takes it — light, dark, or a full set of your own values.
Status pages under your own name
Each site gets a public status page with its own slug, answering “is it down?” before anyone writes in. Probed around the clock, with incidents opened and resolved on the record.
Share links without a login
Send a customer the exact moment in a session — deep-linked to the frame — without provisioning them an account or exposing the rest of the workspace.
Your tokens, our engine.
No theme builder to learn and no build step of ours to run. The embed reads CSS custom properties, so whatever your design system already emits is what it renders.
No npm, no bundler, no JSX. React and the player are baked into the one file.
The rest cover semantics, the chart series, spacing, shadow and motion. Override one and the embed keeps its own defaults for everything else.
A React component with the same props ships in @logclip/widgets, for when you would rather import it than hand-roll a script tag.
One workspace per customer
Each of your customers gets their own site inside your workspace, with its own key, retention and masking configuration. Switching between them is one dropdown, not one login each.
Access scoped to a single site
Per-site grants mean you can invite a customer as a viewer on their own site and nothing else. They see their data; they do not see your book.
One invoice, yours to mark up
You buy the capacity, you set your own price. Billing is per product and metered, so a quiet customer costs you close to nothing and a busy one is priced in advance.
You own the relationship
We do not contact your customers, we do not upsell them, and nothing we send carries our name unless you asked for it. Support questions come to you, and we back you behind the scenes.
What we do not do yet.
You would find these out eventually. Finding them out here is cheaper than finding them out after you have quoted a customer.
- The console itself is not re-brandable. Your team signs in to LogClip; the surfaces you put in front of your customers are the embedded ones above.
- Status pages run on a LogClip slug, not your own domain. Custom domains are not available yet.
- There is no partner portal, no reseller API and no automated provisioning — new customer workspaces are created the same way you would create any site.
- Outbound email — alerts, invitations, usage warnings — is sent from our address, not yours.
Several of these are on the roadmap rather than off the table. If one of them is the difference between a deal and no deal, say so when you get in touch — that is the kind of thing that moves a roadmap.
Tell us what you're building on it.
Reselling arrangements are worked out in a conversation, not a form — how many customers, what needs to carry your name, and what the pricing has to look like for it to work for you.