Purpose
Two things are true at once, and most vendors pick one. Horizontal platforms win on reuse. Governance, identity, approvals, audit, integration and evaluation are the same problem in every business function, and solving them once is worth far more than solving them five times. Vertical applications win on depth. A generic agent platform hands a customer a toolkit and leaves them to invent the entire evidence model for their function. In a regulated domain that is not a head start; it is the whole project. Smaya is built on the position that you need both, in that order.The architecture
Exterview runs on Smaya today. Dotted lines are Upcoming: Gradientflo and later workloads on the same platform.What we deliberately do not build
Not an open agent marketplace
Every agent in the library is one we built, tested and stand behind. An agent making judgments about people carries obligations that cannot be delegated to an unknown publisher.
Not a system of record
Your HRIS holds the employee. We hold the judgment and the evidence behind it.
If the output is a record, it is not ours.
Not a blank development canvas
Customers configure pre-built agents rather than authoring them. The evidence
standard behind an agent is the product, and it cannot be assembled in an
afternoon.
Not autonomous decision-making
Consequential outcomes are decided by named humans. The platform prepares the evidence. That is a design commitment, not a current limitation.
FAQs
Is Smaya a general-purpose agent platform?
Is Smaya a general-purpose agent platform?
It is a horizontal Agent OS with vertical applications on top. The platform capabilities are general; what we ship on them is deliberately domain-specific, because that is where the value and the liability both live.
Related
-
Smaya. The Agent OS.
-
Applications on Smaya.
- Exterview agents.

