Appetize review

Appetize is a hosted cloud service that runs iOS simulators and Android emulators, then exposes them to users through a browser, CLI, or REST API. It is not a mobile SDK or a library you add to an app. The service sits alongside your development and QA stack, providing remote devices for demos, testing, automation, customer support, and AI-agent workflows.

Instead of provisioning local simulators or distributing builds through TestFlight for each audience, teams can share app builds and provide access to cloud devices. The vendor also describes scoped device access for agents and granular permissions for teams. Its homepage names Cursor Cloud, Codex, Claude Code, Devin AI, GitHub Copilot, and custom agents as compatible workflows. AppRecorder and Playwright are listed as automation options on the pricing page. Enterprise plans can include private clouds or self-hosting, so deployment architecture depends on the plan.

The integration surfaces named by Appetize are a REST API and CLI, alongside browser access. The homepage positions both as ways for AI agents and human users to access cloud devices. It names Cursor Cloud, Codex, Claude Code, Devin AI, GitHub Copilot, and custom agents as workflows. The pricing page also lists AppRecorder and Playwright for automation.

The vendor does not name programming-language SDKs on the vendor's site available here. Check Appetize's current docs for supported SDKs, authentication, API request limits, upload workflows, and examples in your language before designing an integration. The same applies to CI/CD: a customer testimonial describes using Appetize in a CI/CD pipeline, but that does not establish a specific built-in CI integration or supported plugin. Treat the REST API and CLI as the documented integration surfaces to evaluate, and confirm whether they expose the device controls your test or agent workflow needs.

The Free plan costs $0 and allows two active devices, 30 minutes refilled monthly, and sessions capped at three minutes. That is enough for brief evaluation, but not sustained automated testing. Starter costs $89 per month, or $59 per month when billed annually at $708 per year. It includes three active devices, 500 minutes, and unlimited session length. Premium costs $449 monthly, or $319 per month billed annually at $3,828 per year; it raises the cap to 16 active devices with the same included minutes.

Starter and Premium charge $0.06 for each minute beyond the included 500. For a production pipeline, estimate runtime as well as concurrent device needs: monthly minutes and active-device capacity are separate constraints. Enterprise has custom device and minute allowances, with pricing by quote; listed options include private clouds or self-hosting and 24/7 support. The vendor does not list Enterprise pricing publicly.

The vendor does not publish an open-source license or source-availability terms on the vendor's site available here. Treat Appetize as a commercial service, not as a library you can inspect and run locally. Enterprise plans list private clouds or self-hosting, but those are custom deployment options rather than a self-service route available on every plan.

The vendor does not publish data-export details here. Before depending on Appetize, ask how to retrieve uploaded app builds, test artifacts, recordings, and any account or device data, and whether exports remain available after cancellation. Migration effort will depend on how much of your workflow uses Appetize-specific CLI or REST API operations. Keep app binaries and test definitions in your own systems, and confirm the API's behavior and data portability before building a large automation layer around it.

The published plan limits make capacity planning part of the integration. Free allows two active devices and 30 minutes per month, with a three-minute session cap. Starter allows three active devices; Premium allows 16. Both include 500 minutes, then charge $0.06 per extra minute. Appetize does not publish API rate limits, availability targets, or reliability terms on the vendor's site available here, so ask the vendor for those before putting a release gate or customer workflow on the service.

The vendor says teams can use granular permissions to restrict device access, and Enterprise lists 24/7 support. The vendor does not publish compliance certifications or detailed security controls here; confirm requirements for sensitive data, access logs, retention, and deployment location. Also establish how devices are allocated during concurrent jobs and what happens when minute or device limits are reached. Enterprise offers custom capacity and private-cloud or self-hosted options, but those terms require a sales conversation.