Frequently asked questions about EvoStudio.
Short, honest answers about deployment, billing, retries, and how to get human help when something goes sideways. If your question isn't covered, our support team is one click away.
Short version: deploying is free.
We never charge credits for the deployment process itself. If a deploy fails, just retry — no penalty, no duplicate charges. Credits are only consumed when your agents actually run work.
Deployment & billing
Does deploying an EvoStudio instance cost credits?
No. Spinning up an instance, updating your Engine, installing MCP tools, and binding bots are all free actions. The deployment pipeline runs on us.
Credits are reserved for the part you actually care about — agent inference, image generation, video generation, and other compute-heavy tool calls.
My deployment failed — what should I do?
Just hit redeploy. Most failures fall into one of three buckets:
- Transient infrastructure — a node blipped, a pull timed out, a region was busy. Almost always fixed by a retry.
- Configuration — a missing key, an invalid token, a malformed prompt file. The error banner will tell you which.
- Quota — you've hit the instance limit for your plan. Visit Billing to upgrade or free up a slot.
Retrying is safe. If three retries in a row fail with the same error, contact our support team — we'll dig into the logs for you.
Will redeploying double-charge me or duplicate my data?
No on both counts. Redeploys reuse the same instance slot, the same chat history, the same memory store, and the same connected bots. You won't see a duplicate instance and you won't see a duplicate bill.
The only thing that changes is the underlying runtime — exactly the part that failed the first time.
So when am I actually charged?
Credits are deducted when an agent does real work: generating a reply, running a tool, producing an image, rendering a video. Costs per tool are listed in the chat header and on your billing dashboard.
Idle instances, failed deployments, and configuration changes never consume credits.
When something looks wrong
Deployment is stuck on a step for a long time — is it broken?
Most deploys finish in 30–90 seconds. If a step has been spinning for more than 5 minutes:
- Refresh the page — sometimes it's just the status stream that hung.
- Click Cancel and redeploy.
- If it still hangs after a clean retry, ping support with your instance ID.
Cancelled and stuck deploys do not consume credits, even if the spinner ran for several minutes.
I can't see my instance after deploy. Where did it go?
Check the instance page — that's the source of truth. If the deploy actually succeeded, your instance is there.
If the page is empty, it means the deploy never reached the "ready" state. Hit redeploy. If the issue persists, reach out with the timestamp of the attempt.
Talk to a human
How do I reach the EvoStudio support team?
Two fast paths — both are read by real humans, not bots:
- Email [email protected] — best for billing, refunds, and anything that requires account access.
- Discord discord.gg/YGn4f3rD9q — best for live debugging, quick questions, and meeting other builders.
To help us help you faster, include:
- Your instance ID (visible on the instance page)
- The exact error message or banner text
- Approximate timestamp of the failure (and your timezone)
- What you were trying to do — deploy, bind a bot, install an MCP, etc.
Response times: Discord replies are usually within a few hours during weekdays. Email is answered within one business day.