Can I test ModelRiver without real provider keys?
Yes. Create a workflow with a structured output and no provider credentials. ModelRiver can synthesise schema-compliant fallback responses for testing.
How many workflows can I create?
As many as you need. Use clear naming conventions and organise by team or feature for easy discovery.
Do you support streaming responses?
Streaming is not available yet. Let us know if it is critical for your use case; it helps prioritise the roadmap.
How should I separate environments?
Create distinct projects (for example, “Production” and “Staging”) and issue dedicated API keys per environment. This keeps credentials, logs, and analytics isolated.
What data does ModelRiver store?
Request payloads, responses, cached data, and token usage metrics are stored for observability and troubleshooting. Purge logs as required by your retention policy.
How do I rotate provider credentials?
Update the credential under Settings → Providers. ModelRiver encrypts the new value immediately.
Can I export logs?
Yes. Use the dashboard export tools or contact support for automated exports and SIEM integrations.
Where can I see the roadmap or changelog?
Major updates appear in the dashboard announcements. Ask support about joining the customer Slack channel for early insights.