Poliglot Inc. · Delaware PBC
Amplifying human agency.
Poliglot builds the engine for a more intentional and productive society. Technology that liberates individuals and businesses to focus on the creative, strategic, and high-leverage work only humans can do.
§01
The thesis
Enterprise software is entering its first real paradigm shift since SaaS. AI has collapsed the cost of building software and is about to make maintenance the dominant cost center. The architectural response is not to generate more applications, but to stop.
We think the next unit of enterprise software is the operating model itself: machine-readable, human-readable, executable, run inside an OS where the AI is resident and extends the model as the work demands. This is not another application or agent framework; it is an OS where data and code are the same thing, and where the business and the software stop drifting apart. Poliglot builds that OS.
Read the full paper§02
What we build
Poliglot OS is the first Poliglot product: a living application layer. One resident AI inhabits a symbolic runtime assembled from your organization's codified operating model and executes deterministic programs against every system of record your business actually runs on. No migration, no new protocols, no mesh of specialist agents coordinating through prompts. The customer codifies the operating model. The runtime makes it executable.
See how Poliglot OS works§03
Our charter
We codified our mission into our articles of incorporation.
To foster a more intentional and productive society by developing technological innovations that amplify human agency, liberating individuals and businesses to focus on high-leverage creative, strategic, social, and value-driven endeavors.
Poliglot Inc., Articles of Incorporation
Poliglot is a Delaware Public Benefit Corporation. The public benefit above is not adjacent to our commercial work. It is our commercial work. Every design decision in Poliglot OS, every system mapping in our catalog, every workflow we automate serves the same end: concentrating human effort at the layer where human judgment is most valuable, and letting the runtime handle the rest.
We chose the PBC structure to make that commitment enforceable by charter rather than dependent on culture or leadership continuity. We're in the company of Anthropic, Hugging Face, and a growing share of frontier technology companies who made the same choice for the same reason: the thing we're building changes how organizations coordinate, and we want the directors of this company (now and after us) to be legally obligated to hold that trajectory.
§04
How we work
Architecture over marketing.
The runtime's design decisions are published in full at /develop before we've sold a line of software. If the architecture doesn't stand up to a senior engineer's scrutiny, nothing else matters.
Imposed, not inferred.
We believe the operating model should be authored by the organization running on it, not discovered by an AI modeling the organization's chaos. Our architecture is a bet on that distinction.
Open where it's built. Commercial where it's run.
The runtime, the matrix specification, the catalog, and the authoring tools are open source. The hosted Matrix Registry and Poliglot OS are commercial. The line is drawn deliberately and will not move toward enclosure as we scale.
Amplify, don't replace.
The resident AI operates inside the operating model the organization has authored. Humans stay in the loop where judgment matters; the runtime takes care of everything downstream. We build to make the people we sell to more capable, not less.
§05
Team
Andrew Perera
Founder & CEO
Andrew spent five years building internal operations and AI systems for some of the largest aerospace and financial services companies. He watched complex organizations forced into a tradeoff between control, accountability, and scale. And he saw AI start to dissolve the ceiling on what one person could attempt on their own. Poliglot closes the gap between the ambition people can now hold and the systems that still struggle to support it.
§06
Trust
We're building infrastructure that executes operational decisions across the systems our customers depend on. That work carries a duty of care. Our current security posture, deployment options, and compliance roadmap are published in full: what's in production today, what's in development, and what's on the roadmap.
Full security & trust reference