We'd rather earn a logo than buy one.
Pearl is in early access. We don't have a wall of customer logos to show you. We have a small group of design partners we're shipping with, and a product you can try right now.
Where we are
Pearl IDE shipped to early access in 2026. We've been onboarding teams one at a time — engineering shops who want an AI-native editor with serious diff discipline, and developers who've outgrown the limitations of single-vendor AI tools.
Most of our early users haven't agreed to be public references yet. That's by their choice, not ours — we're not in the business of using customer logos as marketing before the relationship deserves it.
What we share — when we share it
When a design partner agrees to a public case study, what you'll see on this page is:
- Their name and the team they're on.
- The specific Pearl feature that mattered to them — Scout modes, inline diff, multi-provider, project memory, something else.
- A real quote (their words, not ours) about what changed.
- A short paragraph from the engineer who shipped against Pearl day-to-day.
That's it. No fake testimonials. No "thousands of developers." No anonymous "Senior Engineer at Fortune 500."
If you're already using Pearl
Tell us how it's going. We answer every email. If you want to be a public reference later, we'll work with you on the timing and the framing — and we'll respect a "not yet" or a "never" without follow-up.
Email hello@pearlfibers.com with "design partner" in the subject. We'll set up a 30-minute call this week.
What you actually get.
Direct line to engineering
Slack or Discord channel shared with the team building Pearl. Same-day reply during business hours. No ticket queue.
Features built for you
Real workflow problems get prioritized. If you tell us the missing piece, we usually ship it within a release or two.
Pricing that reflects the trade
Design partners pay less than retail in exchange for the feedback. The exact terms depend on the engagement — we negotiate them in the first call.
Early access to new providers
When a new model lands or a new provider integrates, you get it first — usually before the public release notes.
What we won't claim on this page
- ❌ A made-up customer count. Our number is small and we know it.
- ❌ Anonymous quotes. If we can't attribute it, we don't run it.
- ❌ Logos of companies that "use Pearl" because one engineer there ran it once.
- ❌ "Trusted by teams at [recognizable name]" without the team's permission.
These tactics work in the short term. They cost trust in the long term. We're building for the long term.