We're shipping the editor we wanted to use.
Pearl IDE is built by a small engineering team at PearlFibers. We use it every day, ship to it every week, and answer your support email ourselves.
What we believe
AI shouldn't be a sidebar. It should be a first-class part of the editor — with its own modes, its own diff renderer, its own memory store. The bar isn't "AI plugin works" — it's "the whole editor is better because AI is in it."
We don't believe in dark patterns. No surprise writes. No "we have a free tier, here are the asterisks." No premium-model gating to push you up a SKU. If we add a feature, it's on every paid plan.
And we think the developer using the tool should be the one who's most informed about it. So we tell you what the tool is — and what it isn't — on the Scout page.
Who builds Pearl
PearlFibers is an engineering team based in Baghdad, Iraq. Pearl IDE is one of the products we ship — alongside Loop (collaboration platform), PearlGit (source hosting), and Peak AI (the AI chat product). Pearl is the editor we use to build all of them.
We're not venture-backed. We're not racing to a hype-cycle exit. We're trying to build durable software for developers who want a serious editor with serious AI on top — and bill them honestly for it.
How we work
- Ship weekly. Stable, Preview, and Next channels move on different cadences. The changelog is the ground truth.
- Sales is engineering-adjacent. Pricing conversations happen with people who can answer technical questions in the same call.
- Support is the team. The person who replies to your support email is also the one who'll fix the bug if there is one.
- We don't train on your code. Ever. See how we handle data →
Contact
- General: hello@pearlfibers.com
- Sales: /pricing → contact sales
- Security: security@pearlfibers.com
- Press: press@pearlfibers.com