Residents find the record. Then understand it.
Search by address or record number, move between an interactive map and an equal list, follow the workflow, and get a plain-language explanation—without creating an account.
Public records, made public
Give every resident a clear answer.
Turn permits, planning, code, fire, and licensing records into one fast, accessible civic experience—without replacing the systems your team already trusts.
- Accela-ready
- WCAG 2.1 AA by design
- Your data stays yours
01 Connect your records 02 Prove the experience 03 Publish with control
Search address or record number
Live activity 248 records
New commercial build 112 Market Street BD-26-0142 · In review
↗ Planning application 8 Willow Avenue PL-26-0087 · Approved
↗ Business license 45 Oak Lane BL-26-0319 · Active
↗ One front door for
PlanningPermittingCodeFireLicensingPublic works
The standard is set
Accessibility belongs in the architecture, not the backlog.
The DOJ’s updated Title II rule sets WCAG 2.1 Level A and AA requirements, with compliance dates beginning April 26, 2027. Aedilio gives every map an equivalent keyboard- and screen-reader-friendly list from day one. Read the DOJ fact sheet
The public experience is the product
Make transparency feel effortless.
Aedilio turns the same operational data your teams already manage into useful, plain-language answers for residents, applicants, leaders, and staff.
Leaders see the work moving.
Public scorecards make volume, status, and turnaround visible. Staff views surface sync health, quality issues, and bottlenecks before they become meeting-room surprises.
IT keeps control.
Your canonical records, APIs, and configuration remain portable. Provider adapters isolate source systems; exact tenant boundaries, audit trails, and roles are built into the platform.
One connected platform
From system-of-record to source of clarity.
Aedilio sits above the tools you already use and publishes only what the public is meant to see.
Your systems
A
AccelaPermits and workflows
✓ CSV
File importsHistorical or one-off data
✓ Future systemsThrough a stable adapter
+ A
Aedilio Canonical civic data - Normalize
- Protect
- Explain
Every audience
⌖
Public portalMap, list, details
◎
Resident alertsAreas and records
▦
Staff operationsHealth and scorecards
↗
Open dataAPI and exports
Open by default
Public fields stay browsable. Accounts unlock alerts and convenience—not transparency.
Grounded, not guessed
AI features retrieve live records and cite them. Deterministic search stays available.
Multi-city ready
Branding, modules, policies, domains, and access remain isolated per organization.
Observable by design
Freshness, sync results, health, and change history are visible instead of assumed.
Built to be verified
SSR Fast first response AA Accessibility gates API Portable public data LOG Observable syncs
Built around the people doing the work
One platform.
Different wins.
The public sees one clear front door. Every internal stakeholder gets the outcome they care about.
For executives & council
Answer the room with evidence, not a follow-up.
See permit activity, service levels, and data freshness at a glance. Share a public link that shows exactly what you see.
- Public, meeting-ready scorecards
- Clear service and turnaround trends
- One source for resident-facing answers
Public trust signalFresh data.
Visible provenance.
Visible provenance.
For IT & GIS
Integrate once. Keep ownership for the long run.
Stable adapters isolate vendors from your public experience. Configuration, secrets, access, and audit history stay governable.
- Canonical, portable civic data
- Exact tenant and role boundaries
- Open APIs and standards-based exports
Architecture principleOwn the data plane.
For department teams
Let the portal answer the repeat questions.
Residents can follow the status, workflow, contact, and context themselves—while staff keep working in the system of record they already know.
- Plain-language record explanations
- Public filters, details, and deep links
- Alerts that reduce manual status updates
Operating goalFewer calls.
Better answers.
Better answers.
For residents & applicants
Find what is happening without learning government jargon.
Search the entire public dataset, move between map and list, subscribe to an area, and see when the data was last refreshed.
- No account wall around public records
- Keyboard- and screen-reader-complete
- Mobile-first, multilingual foundation
Experience promiseThe answer is public.
Accessibility that can be demonstrated
“Compliant” should come with receipts.
Aedilio treats WCAG 2.1 AA as an engineering constraint: semantic server-rendered pages, an equal list for the map, keyboard-complete controls, tested contrast, live status announcements, and automated accessibility gates in delivery.
01Equivalent experiences
No essential record is trapped inside a visual map.
02Automated guardrails
Author-time rules and axe checks catch regressions before release.
03Human verification
Manual keyboard and assistive-technology testing remains part of launch.
A rollout your team can see
Go live in measured steps.
We start with your real source data, publish behind a controlled review gate, and launch only after content, policy, and accessibility checks are complete.
- 01
Connect
Validate source access, map raw statuses, and run a sample sync without touching the system of record.
Data contract - 02
Configure
Set branding, public fields, modules, contacts, map behavior, roles, and launch domains.
Tenant workspace - 03
Prove
Review real records, validate redaction, test assistive technology, and reconcile sync results.
Acceptance evidence - 04
Launch & improve
Move to your domain, monitor freshness and health, then add alerts, AI, and open-data features.
Governed releases
A different ownership model
Stop renting the answer.
A public portal can be more than a hosted map. It can become civic infrastructure.
| Capability | Typical hosted portal | A Aedilio |
|---|---|---|
| Public data access | Useful features may sit behind an account | Public by defaultProtect only what policy requires |
| Data ownership | Vendor-managed product and pipeline | Your canonical storePortable records and open exports |
| Map accessibility | Alternative experience varies | Equal map and listDesigned and tested together |
| Artificial intelligence | Generic or unavailable | Grounded and citedProvider-agnostic, with a non-AI path |
| Growth | One portal, one contract | Multi-tenant foundationShare infrastructure without sharing data |
Pricing without theater
See the scope before you see the number.
We price around the complexity of the rollout—not the number of staff who need to do their jobs. Your proposal separates implementation from ongoing operations, and every assumption is visible.
✓ No per-seat transparency tax ✓ Implementation and operations separated ✓ Assumptions documented before procurement
Build a rollout plan
Illustrative rolloutChoose a starting profile
Scope preview Recommended starting point
Focused public launch
Prove the model with one high-value public workflow and a controlled path to expand.
Sources1 system
Coverage1–2 modules
Operating modelManaged
- Public map, equal list, and record detail
- Brand, field-policy, and accessibility configuration
- Launch evidence and governed handoff
Every proposal includes Implementation + ongoing operations, stated separately
Straight answers
Before you ask.
Have a more specific question? Include it in your launch request and we’ll answer it directly.
Does Aedilio replace Accela?
No. Accela remains the system of record. Aedilio synchronizes, normalizes, protects, and publishes selected data through a public experience and operational views.
Can we start with one department?
Yes. A focused launch is often the safest path. Modules, public-field policies, contacts, and coverage dates are configured independently, so the platform can expand without a rebuild.
Is accessibility guaranteed by the software?
No product alone can guarantee legal compliance. Aedilio is engineered around WCAG 2.1 AA patterns and automated gates, then paired with content, configuration, manual testing, and launch evidence.
What does “grounded AI” mean?
The model never invents public records. It translates questions into validated searches or explains retrieved records, with links back to the underlying record. The deterministic search and raw data remain available.
Can the platform use our domain and branding?
Yes. Each tenant has isolated branding, modules, field policies, contacts, locales, map settings, and verified domains. A shared platform does not mean a generic public experience.
Start with your real constraints
Let’s map the shortest path from records to public clarity.
Tell us where your data lives and what residents need to understand. We’ll come back with the right discovery questions—not a generic deck.
01 30-minute working session 02 Technical fit and risk review 03 Clear scope and next decision