- You can learn about features planned in future versions
- You can track version-based development plans
- You can learn the feature request submission process
- You can see the removal timeline of deprecated features
- You can track version release calendar
Important Note: Plans in the Roadmap may change. Priorities can be updated based on user feedback and technical requirements.
Version-Based Roadmap
2026 Roadmap
2026.1.0 (January 2026) - Planned Features
-
Advanced API Gateway Features
- GraphQL Gateway support
- WebSocket API Gateway support
- gRPC Gateway support
- Advanced routing algorithms
-
Advanced Monitoring and Observability
- Distributed tracing support (OpenTelemetry)
- Advanced metrics and alerting
- Custom dashboard creation
- Real-time log streaming
-
Security Improvements
- Zero Trust Architecture support
- Advanced threat detection
- API security scanning
- Compliance reporting improvements
2026.2.0 (February 2026) - Planned Features
-
Kubernetes Native Improvements
- Operator improvements
- Auto-scaling improvements
- Service mesh integration (Istio, Linkerd)
- Multi-cluster management
-
API Portal Improvements
- AI-powered API documentation
- Interactive API testing
- API versioning management
- Developer onboarding improvements
-
Integration Improvements
- New connectors
- Event-driven architecture support
- Message queue integrations
- Streaming data processing
2026.3.0 (March 2026) - Planned Features
-
Performance Improvements
- Hazelcast cluster optimizations
- Database query optimizations
- Cache strategy improvements
- Network performance optimizations
-
Management and Operations
- Self-service portal
- Automated deployment pipelines
- Configuration management improvements
- Disaster recovery improvements
2026.4.0 (April 2026) - Planned Features
- New Features
- API Marketplace
- API monetization
- Advanced analytics and reporting
- Machine learning integrations
Long-Term Plans (2027+)
-
Cloud Native Transformation
- Multi-cloud support
- Serverless architecture support
- Edge computing support
-
AI/ML Integrations
- AI-powered API recommendations
- Automated API testing
- Intelligent rate limiting
- Anomaly detection
-
Advanced Integrations
- More third-party integrations
- Industry-specific solutions
- Compliance frameworks
Feedback and Feature Request Process
Submitting Feature Request
The Apinizer team evaluates user feedback and feature requests. To submit a feature request:- Support Portal: You can create a feature request through the support portal
- Email: You can send an email to [email protected]
- Community Forum: You can share feature requests on the community forum
Feature Request Evaluation Criteria
Feature requests are evaluated according to the following criteria:- User Need: How many users need this feature?
- Business Value: How much value does this feature add?
- Technical Feasibility: Is it technically feasible?
- Platform Compatibility: Is it compatible with Apinizer’s overall vision and architecture?
- Resource Requirements: What resources are needed for development?
Feature Request Statuses
- Under Review: Feature request received and being evaluated
- Planned: Feature request accepted and added to Roadmap
- In Development: Feature development has started
- Beta: Feature is in beta stage and being tested
- Released: Feature is released and available
- Rejected: Feature request rejected for technical or strategic reasons
Deprecated Timeline
2026 Timeline
Q1 2026
-
Old Authentication Methods
- Deprecated: 2024.1.0
- Will be removed: 2026.1.0
- Alternative: OAuth 2.0, JWT
-
Legacy Rate Limiting Policy
- Deprecated: 2024.1.0
- Will be removed: 2026.1.0
- Alternative: Enhanced Rate Limiting Policy
Q2 2026
-
Old Cache Configuration
- Deprecated: 2024.2.0
- Will be removed: 2026.2.0
- Alternative: Hazelcast Distributed Cache
-
Legacy API Gateway Configuration
- Deprecated: 2024.3.0
- Will be removed: 2026.2.0
- Alternative: New API Gateway configuration
Q3 2026
- Old Monitoring APIs
- Deprecated: 2025.1.0
- Will be removed: 2026.3.0
- Alternative: New Monitoring APIs
Q4 2026
- Old Policy Engine
- Deprecated: 2025.2.0
- Will be removed: 2026.4.0
- Alternative: New Policy Engine
Deprecation Process
- Deprecation Announcement: Feature is marked as deprecated and announced
- Warning Period: Users are warned and recommended to transition to alternative solutions
- Migration Support: Migration guides and support are provided
- Removal: Feature is removed on the specified date
Version Release Calendar
Apinizer aims to release a new major version every 4 months:- Q1: Major version in January
- Q2: Major version in February
- Q3: Major version in March
- Q4: Major version in April
Roadmap Updates
Roadmap is regularly updated. Updates occur:- When each major version is released
- When important changes occur
- Based on user feedback