01 / PLAN
Open Source
An Apache Software Foundation project maintained by its open-source community- Apache Flink job submission and basic management
- Apache Flink multi-version support
- Apache StreamPark basic capabilities
Commercial guide · Pricing
Price the operating model—not the feature bundle.
Pricing follows production scope, deployment responsibility, and support needs. The architecture review defines the proposal.
02 / PLAN
Standard
Enterprise Flink operations for a dedicated production team- Enterprise enhancements built on the Apache StreamPark foundation
- Bug fixes and vulnerability notifications
- Deployment across on-premises, BYOC, and cloud environments
- Elastic scaling based on load to improve resource utilization
- Multi-node deployment for high availability
- Ready-to-use source and sink connectors
- Platform and job-level monitoring metrics
- Job log storage and end-to-end observability
- Integrated development and debugging workflow
- Realfuture technical support
03 / PLAN
Enterprise
Advanced delivery, integration, and support for larger or critical estates- Includes all Standard edition features
- 36 months of extended kernel support
- Production migration assistance
- Job parameter tuning and troubleshooting guidance
- AI-assisted job development and troubleshooting
- Additional built-in connectors for broader data integration
- Compatibility with domestic technology stacks
- Scoped customization services
- Role-based product and operations training
- Integration with enterprise identity, operations, and governance systems
Commercial features and services depend on the selected release and agreement. Confirm supported components, maintenance term and service hours in the proposal. Additional integration and customization are scoped separately.
Capability comparison
Apache StreamPark vs. Realfuture Enterprise.
Compare 42 capabilities across deployment, development, operations, and governance.
Apache StreamPark is an independent Apache project, not a free Realfuture edition. Community installation references use the documented 2.1.5 examples; capabilities vary by release. This is a guide to product scope, not a release certification matrix. Community installation documentation · Compatibility and evaluation guide
| Category | Capability | 01 / OPEN SOURCEApache StreamPark | 02 / REALFUTUREEnterprise |
|---|---|---|---|
| 01Software | Flink and CDC | Connects to supported Apache Flink runtimes. Flink and Flink CDC are maintained by their own communities. | Commercially maintained Flink, Flink CDC and connector branches, alongside the platform. The delivered release defines enhancements, component versions and maintenance scope. |
| Development and operations | Application development, deployment and operations, including Flink SQL and JAR workflows. | Catalog management, SQL validation and previews, visual ETL, CDC, JAR and Git workflows, with resources, publishing and job operations. Native SQL uses supported database catalogs; visual ETL currently supports one sink. See the development guide for workflow boundaries. | |
| 02Deployment | Installation and platform database | Self-hosted installation, including Docker Compose. MySQL and PostgreSQL are documented platform database options. | Deployment planning and platform enhancements for the customer environment. Platform HA, database adaptations and installation responsibilities are scoped for the deployment. |
| Runtime compatibility | Supports multiple Flink versions and deployment modes, depending on the StreamPark release. | Management of connected runtimes, with commercial enhancements for selected components. Confirm Flink, CDC, JDK, connector and infrastructure versions together. Enhanced features may require component upgrades. | |
| 03Integration | Connectors and ecosystem | Uses connectors and ecosystem components available for the selected runtime. | Connector and ecosystem enhancements maintained as part of the commercial product. Source and sink directions, data types and schema-change behavior depend on the connector and version. |
| Enterprise systems | Community capabilities and integration options vary by release. | Platform integration and additional engineering services can be included in the proposal. Agree on identity, API, monitoring and other integration requirements before a proof of concept. | |
| 04Support | Maintenance and assistance | Community releases, public issue tracking and community assistance. | Enterprise technical support and maintenance for the agreed software scope. Covered versions, maintenance term, service hours and response targets are defined in the agreement. |
| Migration and delivery | Documentation and community resources; deployment and validation remain with the operator. | Deployment, migration, training and tuning services can be scoped with the team. Validate representative jobs, state compatibility and rollback steps in the target environment. |
What shapes the proposal
Four inputs shape the proposal.
Commercial scope follows the operating responsibilities Realfuture takes on.
Production scope
Workload count, criticality, teams, and connected runtime environments.
Deployment model
Private cloud, customer cloud, hybrid topology, and operational ownership.
Support level
Response expectations, support lifecycle, migration, and production assistance.
Additional delivery
Optional connectors, integration, training, and scoped customization.
Need a budgetary range first?
Share job count, runtime clusters, deployment boundary, and support needs. We’ll recommend the right tier and define the inputs for a scoped proposal.