Wicked for Good runtime with preview delivers a streamlined way to test and experience the platform before full commitment. This overview explains what to expect from session length, feature access, and performance during the preview window.
Preview sessions are designed to mirror the full runtime environment so teams can evaluate fit, performance, and integration early. Below is a detailed summary of how time, features, and limits are structured during the preview phase.
| Session Type | Duration | Feature Access | Data Limits |
|---|---|---|---|
| Preview Runtime | 45 minutes per launch | Core workflows and APIs | Up to 10,000 records |
| Extended Preview | 2 hours on request | Most premium features with approval | Up to 100,000 records |
| Production Runtime | Continuous execution | Full feature suite | Based on plan quota |
| Sandbox Preview | Indefinite for testing | Read-only templates | No live data writes |
Runtime Performance in Wicked for Good
Wicked for Good runtime performance during preview is optimized for fast feedback on data transformation, connector response, and rule execution. Teams can run representative workloads to measure throughput, latency, and error handling under near production conditions.
Preview Feature Coverage
Not all premium capabilities are available during the preview, but the platform exposes critical modules such as orchestration, monitoring, and alerting hooks. This enables realistic validation of governance and compliance requirements before licensing decisions.
Security and Isolation
Preview environments use network isolation, scoped credentials, and audit logging to protect sensitive data. Role based access controls ensure that testers interact only with approved datasets and integrations, maintaining security while enabling experimentation.
Deployment and Scaling Insights
During wicked for good runtime with preview, scaling behavior is approximated through limited concurrency and resource caps. Observing how jobs queue, backpressure, and recover helps teams size future deployments and plan for growth.
Operational Guidance for Wicked for Good Runtime
- Use the 45 minute preview window to validate end to end pipelines.
- Request extended sessions when testing large datasets or complex rules.
- Monitor resource usage to estimate scaling needs for production.
- Leverage read only templates in the sandbox for safe exploration.
- Plan licensing based on observed throughput and concurrency patterns.
FAQ
Reader questions
How long does each preview session last?
Each preview session runs for 45 minutes per launch, with the option to request up to 2 hours for deeper evaluation.
Can I access premium features during the preview?
Core workflows and most premium features are available, although some advanced modules may require approval or be read only in the sandbox.
What are the data limits for preview usage?
Standard preview sessions support up to 10,000 records, while extended previews can process up to 100,000 records when requested.
Is my data kept separate and secure in preview mode?
Yes, preview environments use network isolation, scoped credentials, and detailed audit logs to keep test data secure and separate from production.