Update on Arize-hosted Phoenix Cloud Storage Pricing Plans

Seth D. · 2025-12-03 08:38:24.673922+00

I see that the mention of additional paid storage for the Arize-hosted Phoenix Cloud offering seems to have been pulled from the pricing page - can I assume that means you're not likely to offer that any time in the near-term? (Some of the back and forth here https://arize-ai.slack.com/archives/C04R3GXC8HK/p1750774150763159 seemed to indicate that it might be on offer soon, but perhaps thinking has changed?)

Update on Arize-hosted Phoenix Cloud Storage Pricing Plans | Arize AI Community

Jonathan B.
·
Hi Seth D. the pricing page was pulled as we are planning on offering additional storage for free! For now its on a request basis so feel free to reach out if needed.
Seth D.
·
Well, that's a better answer than expected, thanks!
Jonathan B.
·
linking here for the storage increase request
Seth D.
·
Sure. (Sorry, not sure when you guys cut over from one to the other - I think our account dates to ~Feb or March?)
Kiko C.
·
No worries at all. Yes as I suspected you’re not on the new version. We’re working on migrating people to the new version but it’s proving itself challenging. The easiest thing we can do is to delete your current account and create it again. That way you’ll have all the goodies of the new version (which I can describe if you don't know them). This way you will lose your data though. So a half way measure is for you to create a new account with a different email, we recommend just aliasing your email: seth+alias@gmail.com . That way you can log into both, start migrating your operations to the new, and eventually not care about the old and we can delete it.
Kiko C.
·
What do you think?
Seth D.
·
Yeah, if there isn't likely data-preserving migration path on the immediate horizon, that may be the best way forward. Can trace exports be done remotely (a la px.Client().get_trace_dataset().save(...) or similar?) targeting the older version used by my present account? I'm sure if it was as simple as just kicking things out to files, massaging them, and loading them back in, you'd be doing that, so I don't expect to be able to flush them into a newly established environment, but I would at least like to keep them around to preserve the possibility of launching a local old version if I ever need to look at something in there.
Kiko C.
·
There are nuances on migrating data, devil is in the details. There's a few things we can't preserve yet, we're working on it
Kiko C.
·
Login again with an aliased email or a new one and you should see a settings page with API keys and users
Kiko C.
·
In addition, you should see a "Management Console" link to go to the management page where you can create new phoenix spaces (different phoenix apps). We currently limit to 2 spaces but we're gonna improve this
Kiko C.
·
You will be able to invite users to collaborate as well
Kiko C.
·
And if you were to fill the disk, let us know, we will be able to help you then
Seth D.
·
re: migration details - no doubt - totally understand there are ton of weird corner cases for you guys to run down that may or may not all be worth the effort for you all. I'll check out the new stuff, thanks - and I expect over time, we can just clobber the old one, though I would like to try and export whatever (if anything) we can from it. Do the trace export facilities detailed in the docs apply to hosted offerings? (Just get an HTTP 403 on the attempt presently, but maybe that's just because we've maxed out storage?)
Seth D.
·
Sure - as regards headers, it's via an environment variable (PHOENIX_CLIENT_HEADERS with a value of api_key=<PRIVATE_CRUD_HERE>) The call attempted that's indicating an underlying HTTP call got a 403 is just what's shown @ https://arize.com/docs/phoenix/tracing/how-to-tracing/importing-and-exporting-traces/extract-data-from-spans#save-all-traces
some_trace_id = px.Client().get_trace_dataset().save(directory=directory)
Seth D.
·
Don't also need to be supplying a OTEL_EXPORTER_OTLP_HEADERS do I?

23 comments