Permiso combines a deterministic rules engine, a multi-model AI layer, and a workflow engine into one platform — wired into your authoritative systems and your reviewer experience.
Applicants submit through a single interface that works on any agency website, mobile or desktop. Permiso composes the form dynamically from your application model, including fields for any dependent permits the application triggers.
While the applicant types, Permiso runs deterministic rule checks and field-level AI reviews. Issues surface during drafting, not after submission. Most rejections never happen because most rejections were correctable.
On submission, Permiso routes data to your authoritative systems through adapters, evaluates rules, runs AI analysis where rules can't decide, and produces a typed decision with citations and confidence scoring.
Your reviewers see a pre-assembled decision package with suggested conditions, evidence, and precedent. They accept, modify, or reject each suggestion. Human authority holds at every step.
Most permitting AI products run every check through a flagship language model. That's expensive and overkill — most permit checks are deterministic. Permiso routes work through four tiers, in order, and stops at the first one that can answer.
A deterministic rules engine handles unambiguous checks. Sub-millisecond response. Zero token cost.
For routine reasoning that exceeds simple rules, Permiso uses small, self-hosted language models. Cheap and fast.
For complex analysis with retrieval, Permiso uses your agency's preferred flagship model. Used sparingly, by design.
High-risk Tier 3 outputs pass through a QA model from a different vendor. Two models from the same vendor share the same blind spots.
The cost of a review scales with its complexity, not with your volume. A simple registration costs pennies. A complex multi-permit application costs a few dimes. Run the math against what manual review costs you today.
Every AI output returns a structured response: recommendation, confidence, rationale, and the specific evidence behind it — regulation cited, precedent retrieved, model version, timestamp. Every interaction logs with full context.
When an Inspector General asks how a decision was made, the answer is in the system, not in someone's head. When a denied applicant sues, the evidentiary chain is already assembled.
An architectural property, not a documentation exercise added at the end.
Modern REST and GraphQL APIs. Legacy SOAP services. CSV exports. Event-driven message buses. Manual processes documented in a handbook somewhere. Permiso's adapter pattern isolates the protocol details of each downstream system behind a consistent internal contract.
Modern APIs, native bindings, OpenAPI schemas.
Legacy systems supported through the same adapter pattern.
Submissions queue when downstream systems are offline. No lost work.
Batch exchanges and overnight reconciliation.
A 45-minute briefing tailored to your agency, your authorization types, and your compliance environment. No generic deck.