<@ULVA73B9P> I am on the pro tier but I have maxed...
# marvin-ai
s
@Marvin I am on the pro tier but I have maxed out my usage, are there options to upgrade? and are they self serve?
m
thought for 9.2 seconds
Yes — if you want more usage than the Pro tier includes, your upgrade path depends on what you need. Self-serve option: - In Prefect Cloud, go to Org Settings → Billing → Upgrade at app.prefect.cloud Plan details / pricing: - See prefect.io/pricing If the option you want is not available self-serve (for example, a larger/custom plan or enterprise-style arrangement): - Use prefect.io/contact So: some upgrades are self-serve, and if you’ve outgrown Pro beyond what Billing allows in-app, the next step is the contact form.
s
its urgent since its affecting production, how do I get in touch immediately?
@Marvin its urgent since its affecting production, how do I get in touch immediately?
m
thought for 10.4 seconds
The fastest official path I can point you to is: - Contact sales / team: prefect.io/contact - Check self-serve billing first: app.prefect.cloudOrg Settings → Billing → Upgrade If your production issue is due to a product bug or outage rather than plan limits, you can also check: - Status page: status.prefect.io - Open issues / community support: GitHub issues and GitHub discussions I can’t directly escalate or contact the team for you, but if you tell me what usage limit you hit (for example concurrency, flow runs, task runs, events, etc.), I can help you identify a workaround right now.
s
managed compute hours on the pro plan: 225 hours
@Marvin managed compute hours on the pro plan: 225 hours
m
🔄 Thinking... this may take a while
If you've hit the 225 managed compute hours included with Pro, there is not a special real-time support line I can invoke from here. Your immediate options are: - Try self-serve first: app.prefect.cloud → *Org Settings → Billing → Upgrade> - If there’s no higher self-serve option for managed compute capacity: use prefect.io/contact - Review plan details: prefect.io/pricing If production is blocked right now, the practical workaround is usually to move the affected deployments off managed compute and run them on your own infrastructure via a work pool / worker, so they no longer consume managed compute hours. If you want, I can help you do that quickly and give you the exact steps for one of these: - Docker worker - Kubernetes worker - Process worker / VM-based worker Tell me what infrastructure you have available, and I’ll outline the fastest migration path.