Where Aeion Is Going.

The roadmap below is honest direction, not marketing promises. We commit to ship dates only when work is materially complete; everything else is labeled "in flight" with the realistic state. Priorities shift; we revisit quarterly. If a roadmap item matters for your evaluation, talk to sales — we can usually share more detail in a scoping call than this public page can commit to.

Quarterly roadmap reviews
Public commitments only when work is materially complete
"In flight" status when work is real but ship-date uncertain
"Exploring" status when we're investigating but not committing yet
"Deferred" status when we've decided not to do it in the planning horizon
Enterprise customers get NDA roadmap visibility beyond what's here
Roadmap shifts get changelog announcements

How We Talk About Roadmap

Three statuses we use.

In Flight — Next 1-3 Quarters

Aegis Phase 4 ops surface

Weekly verification cron + auto-generated compliance reports are shipping incrementally. Notification fan-out (22 event types) and 8-tab Aegis Hub at /admin/platform/aegis are in active iteration. Should be feature-complete this quarter.

HITRUST certification

For healthcare-vertical tenants. SOC 2 Type II audit motion is in flight (readiness framework at /compliance/soc2-readiness); ISO 27001 in progress; HITRUST is the next certification investment after SOC 2 + ISO 27001 complete. Engineering work on control evidence is in flight.

Self-hosting operator experience

Self-host on Professional and Enterprise works today but is operator-heavy. We're investing in operator-friendly install scripts, automated platform upgrades, and air-gapped deployment options. Should be more mature by end of next quarter.

AeionClaw skill expansion

8 personas / 47 skills today. We're adding deeper module-specific skills, cross-module memory iteration, and custom-skill creator improvements. Shipping incrementally.

More /architecture deep-dives

Beyond the 6 listed above, we're scoping AI Provider Routing, AeionClaw Architecture, Aegis Phase 2 PITR Internals, and Singularity Adapter Framework. Some land this quarter, others next.

Public partner portal

Mentioned in /partners as "in progress." Deal registration, commission tracking, marketing-collateral library. ETA late 2026.

Exploring — Customer-Demand-Dependent

FedRAMP Moderate certification

Federal government contractors and state/local government customers need it. We're FedRAMP-aligned (NIST 800-53 controls implemented) but not FedRAMP-certified. Decision to pursue formal certification depends on customer-demand signal in the federal space.

Industry-specific case studies

Customer-attribution + brand + creative process to ship 10-15 named case studies across healthcare, fintech, retail, hospitality, construction. Exploring whether to invest in the case-study production cycle this quarter.

Custom-connector framework for legacy / proprietary systems

Singularity ships 103 connectors today. Customer requests for specific legacy systems (mainframes, in-house ERPs, specialty industry vendors) come in regularly. Exploring whether to invest in a customer-extensible connector framework vs continuing to build connectors centrally.

Mobile-builder native build pipeline

Cloud EAS builds work today. Exploring whether to add self-hosted build pipelines for tenants who need full sovereignty on the binary. Likely Enterprise-only.

Aeion-managed vault for backups

Default Aegis posture is Bring-Your-Own-Bucket. Some SMB customers don't want to set up S3; exploring an Aeion-managed vault option as a per-tenant line item.

Vertical-specialty case management

Beyond /legal, we hear from professional services firms (consulting, accounting, agencies) about needing case-management. Exploring whether to build a dedicated /services module or extend existing modules.

Deferred — Not on Near-Term Roadmap

Public app marketplace

No Salesforce AppExchange / Shopify App Store equivalent in scope. Aeion's "every module is included" model conflicts with marketplace economics. We may revisit in 2027+ if customer demand changes.

Indirect-sales channel program

Aeion is sold direct today. Reseller tier exists for agencies (see /partners) but there's no formal multi-tier channel program. Will likely build when revenue justifies the GTM investment, probably 2027+.

First-party hardware

Aeion Bridge integrates with hardware (BLE, POS, OBD-II, NDI, MAVLink) but we don't manufacture or resell devices. Customers buy hardware directly from vendors; Bridge connects. We're not entering the hardware business.

Open-sourcing the platform

Aeion is closed-source SaaS. Sovereignty escape hatches (CMK, BYOB, self-host, full data export) cover the "what if I want my data back" scenarios. We may open-source specific components (e.g. the Bridge agent) but not the platform as a whole.

How Roadmap Shifts Get Communicated

Roadmap is a snapshot. Things change. When they change:

Roadmap for Enterprise Customers

Enterprise contracts include NDA-gated roadmap visibility beyond the public page. Specifically:

Frequently Asked Questions

Because we'd over-commit and we'd be wrong. Software engineering estimates at quarterly granularity are mostly inaccurate; public quarterly commits would erode trust faster than the value they'd provide. We commit when we're materially done.

Talk to sales. For Enterprise customers, we can sometimes negotiate ship-date commitments for high-priority features as part of contract terms. Co-development (see /partners) is the structured path for sponsored work.

Industry-specific compliance certifications (HITRUST, FedRAMP) and vertical-specific module depth (healthcare workflows, legal-practice-management depth, financial-services audit trails). Roughly in that order.

Because public architecture documentation is one of the highest-investment areas of marketing surface. Each architecture deep-dive takes engineering review + writing time. Customers in active evaluation drive prioritization on which architecture page to ship next.

Subscribe to release notes (email release-notes@aeionos.com with "subscribe"). Or watch the specific issue in the public /forge instance once we have public project visibility (in flight).

Not publicly today. Enterprise customers under NDA can get visibility into the relevant epics. We're exploring public roadmap visibility through Forge (see "exploring" above).

Best ways: (1) Be a paying customer — customer requests drive prioritization heavily; (2) Sponsor co-development (Enterprise path, see /partners); (3) Articulate your need in /contact — we file it as evidence even from non-customers and revisit at the next quarterly review.

Yes — and we accept that. The reason: prospect transparency matters more than competitor opacity. Most of what's on this page (architecture documentation depth, certification path, self-hosting maturity) is hard to execute even with a roadmap to copy. Competitors can know the destination; the value is in the engineering required to get there.