Corevia V4 Roadmap: From Production-Ready Framework to Multi-Runtime Application Platform
Corevia V3 is complete and production-ready. Now we're preparing for the next major milestone: Corevia V4.
Corevia was built around a simple idea: modern application development should be modular, predictable, and flexible enough to connect different technologies without introducing unnecessary complexity.
Rather than following a traditional MVC-only architecture, Corevia combines Actions, Flows, Events, durable execution, and explicit cross-runtime contracts.
V3 established the foundation. V4 aims to make that foundation significantly easier to adopt, extend, operate, and scale.
The Corevia V4 roadmap has been finalized, covering 19 major workstreams.
V4 is currently planned, not yet released. The target is to deliver the complete V4 scope as one major public release after implementation and validation.
What Corevia Already Provides
Corevia V3 established capabilities including modular application composition, durable workflows, realtime communication, and multi-runtime integration.
Its architecture includes:
- Modular Actions, Flows, and Events
- Durable workflows and retry handling
- Background execution and worker infrastructure
- HTTP routing, validation, and middleware
- WebSockets and realtime capabilities
- PHP-to-Python interoperability
- Runtime profiles and capability composition
- Deterministic module architecture
- Cross-runtime contracts
- AI-oriented integration capabilities
- CLI tooling and developer infrastructure
Corevia also supports a broader development direction involving Python, JavaScript, React, Dart, and Flutter.
The goal is to let developers build applications using appropriate runtimes while keeping application boundaries explicit.
What's Coming in Corevia V4?
1. A Better Developer Experience
V4 will focus on making Corevia easier to install, configure, test, and upgrade.
Planned improvements include Composer-based distribution, a feature-composition installer, database migrations, seeders, factories, richer database queries, and optional repository/model helpers.
The testing toolkit will expand with HTTP assertions, isolated databases, controlled time, and fake implementations for mail, jobs, and AI services.
Safe upgrades are another important objective. Framework updates should not silently overwrite developer-owned application files.
2. Production-Grade SaaS Capabilities
V4 is planned to introduce stronger foundations for building multi-tenant applications and business software.
This includes server-validated tenant isolation, versioned public APIs, scoped API credentials, quotas, audit trails, and configurable data lifecycle management.
Optional identity extensions will include passkeys/WebAuthn, service accounts, and organization SSO integrations.
These features are intended to support applications such as CRM systems, ERP platforms, business management software, and multi-tenant SaaS products.
3. An Expanded AI Application Platform
AI is one of Corevia's important architectural directions.
V4 aims to extend AI integrations beyond basic model requests.
Planned capabilities include document ingestion, vector-store adapters, structured outputs, retrieval evaluation, and per-tenant usage budgets.
Permission-controlled AI tools will support explicit authorization, bounded execution, and configurable human approval.
The objective is to make AI functionality a controlled part of application architecture rather than giving AI services unrestricted access to business systems.
4. More Reliable Background Operations
Production applications need predictable behavior when external services fail.
Corevia V4 will target improvements such as scheduled jobs, monitoring, failed-job recovery, transactional outbox patterns, signed webhooks, and controlled redelivery.
The roadmap also introduces deadline propagation, cancellation, retry budgets, and circuit breakers.
These mechanisms are particularly important for applications coordinating PHP, Python, background workers, external APIs, and AI workloads.
5. Cross-Platform and Offline Applications
Corevia's multi-runtime direction extends beyond backend services.
V4 plans optional offline synchronization capabilities for Dart, Flutter, and React Native clients.
This includes authenticated change feeds, resumable synchronization cursors, deletion records, bounded offline queues, and documented conflict-resolution behavior.
The goal is to provide a stronger foundation for applications that must work across web, mobile, and disconnected environments.
6. Hosting Portability
One of the most practical V4 objectives is deployment flexibility.
The roadmap targets tested deployment configurations for:
Shared PHP Hosting | VPS | Dedicated Servers | AWS | Azure
Not every application should require Python, Redis, Node.js, containers, or external AI infrastructure.
Optional capabilities should remain optional.
Simple applications should stay lightweight, while complex applications can use additional runtimes and services when required.
7. Observability, Security, and Compatibility
V4 also targets developer inspection tools, production health checks, metrics, distributed tracing, extension compatibility validation, and reproducible benchmarking.
Accessible and multilingual starter applications, including right-to-left layouts, are part of the planned scope.
Performance and security claims will require documented validation instead of relying only on feature availability.
The V4 Release Strategy
Corevia V4 is planned as one complete major release.
Development will be organized internally through reviewable phases covering architecture, distribution, application development, identity, operations, AI, mobile integration, and release acceptance.
Each phase will require relevant testing and validation.
The final public release will target completion of all 19 roadmap workstreams, accompanied by documentation, compatibility checks, deployment testing, and upgrade guidance.
The current target is to complete and launch V4 in the coming weeks.
The release date will depend on implementation and acceptance results.
The Bigger Vision
Corevia isn't intended to become a heavyweight framework that forces every application to use every available capability.
Its architecture is designed around modularity.
A simple application should remain simple.
A complex application should be able to introduce durable workflows, background processing, AI integrations, realtime communication, or additional runtimes without requiring an entirely different architectural foundation.
With V4, the ambition is to bring together developer productivity, reliable execution, production operations, and multi-runtime flexibility in one coherent framework.
Corevia V3 established the foundation. Corevia V4 aims to make that foundation ready for a broader developer ecosystem.
The roadmap is finalized. Development is moving toward the next major release.
Explore Corevia on GitHub:
https://github.com/corevia-framework/corevia
Tags: #php #opensource #softwareengineering #ai
Top comments (0)