What LinearPilot is, and what it isn't

Every company introduction is pulled toward the same three paragraphs: the origin story, the traction, the mission. We are going to skip all three. Two of them we would have to invent, and the third is only worth reading if the product backs it up — so this is about the product and the convictions underneath it, which are the parts you can check.

Mechanically, LinearPilot is a business workspace: 29 built-in apps sitting over one shared data layer, with an AI assistant that can read across all of it and, with your approval, change it. Clients, Drive, Knowledge Base, Calendar, Tasks, CRM, Document Signing, Automation and the rest are apps in the sense of being different interfaces, not in the sense of being different databases. It is sold as one subscription per company.

The first conviction is that your tools should share records rather than sync them. Integrations exist because separate systems keep separate copies, and copies drift; a shared data layer does not have that failure mode because it does not have the copies. This is the least glamorous idea in the product and probably the most load-bearing.

The second is that an assistant which can only talk is a demo, and one that can act without asking is a liability. So reading happens freely, creating is treated lightly, and anything that overwrites or removes something waits for a person to approve the specific change — shown concretely, field and value and record, not as an abstract “the AI would like to do something.”

The third is that a product should say what happens to your data rather than gesture at it. LinearPilot runs AI on named external providers, published on a page you can read. Personal identifiers are masked before a prompt leaves and restored in the answer that comes back. Every outbound call is recorded. AI is off until your company turns it on and off per person until they consent. And where the mechanism is weaker than the marketing word for it, we write the weaker sentence — there is a whole post on this blog whose main job is to correct a sentence we had wrong about our own tenant isolation.

Now the part that tells you more than the convictions do: the things LinearPilot deliberately does not do. There is no public API. Not “coming soon” used as a euphemism — there is no key system, no token issuance, no programmatic access path of any kind. If your plan depends on driving LinearPilot from your own code, LinearPilot is the wrong choice today, and finding that out from a blog post is better than finding it out in week three.

There is no white-labelling. You can set your brand inside the product, and nothing removes the LinearPilot mark. There is no support response-time guarantee, because we are not going to sell a number we have not staffed to meet. And there are no certifications: LinearPilot does not claim SOC 2, ISO 27001, or HIPAA certification, and does not represent that a Business Associate Agreement is in place. Specific controls are implemented and we will happily enumerate them — encryption at rest, multi-factor authentication, crypto-shredding on deletion, audit logging. A framework being met is a different claim, and we are not making it.

Saying that out loud costs something, and it is worth being clear about why we do it anyway. The alternative is that a buyer discovers it during procurement, having already spent their time on us — which is a worse outcome for them and, eventually, for us. And a product that will tell you what it cannot do has said something checkable, which is the only thing that makes the rest of what it says worth anything.

What is here today, concretely, is the workspace and the apps, an assistant that works across them with an approval step in front of anything destructive, a mail client whose AI writes drafts and leaves the sending to you, sandboxed code execution for real analysis, and voice. The free plan is a permanent plan rather than an expiring trial — new signups do get a one-week credit uplift on top of it, but the plan itself stays after that week regardless. Everything above has a post on this blog with the mechanism spelled out.

We are not going to promise you a roadmap here, because a roadmap in a company introduction is the cheapest thing to write and the easiest to quietly abandon. The best argument we can make is the product. The second best is that every claim on this blog is one you can go and check.