Frequently asked questions

No. If you can describe what you want, you can build and ship. Coding knowledge helps you go faster, but it is not required.

You can build everything from simple landing pages to full applications with complex logic, a server, and a database.

AppDeploy works with ChatGPT, Claude Desktop, Claude Web, Claude Code, Figma Make, Cursor, Codex, and any other agent that supports MCP (Model Context Protocol).

It depends on your agent. Use the setup guide for your platform:
- ChatGPT
- Claude (Web/Desktop)
- Codex App
- CLI coding agents
- Figma Make
- Antigravity
- Cursor (one-click install link)

No. AppDeploy is designed so you can build and deploy from the AI chat itself without Git, an IDE, or local tooling.
Some agents require a one-time connector or MCP setup, but day-to-day use happens in the conversation.

No. It is built to work for non-technical builders, but developers can use it to move faster, inspect the code, iterate in chat, and export the source at any time.

AppDeploy hosts your app for you automatically on scalable cloud infrastructure and gives you a live URL. You do not need to pick a hosting provider or set up hosting yourself.

Apps typically go live within a few seconds. You will see progress in your AI chat and get a link once your app is ready.

Yes. You can ask the AI assistant to pull all source code at any time, including the latest version or a previous one.

Yes. You can continue prompting the AI to change the app after it is live, and AppDeploy will deploy updated versions as you iterate.

Yes. Every deploy is stored as a version, and a known-good version can be re-applied if a later change regresses.

AppDeploy uses layered controls including tenant isolation, short-lived credentials, sandboxed execution, encryption in transit, encrypted storage where supported, and infrastructure-level policy enforcement.
For more detail, see Security and How AppDeploy protects app and user data.

Do not submit secrets, payment card data, government IDs, or other restricted data in prompts, project files, or messages.
AppDeploy does not support HIPAA workloads and should not be used for PHI or ePHI unless agreed separately in writing under a BAA.

Build logs are retained for up to 30 days, security and access logs for up to 90 days, and backups for up to 30 days after deletion on a rolling basis for disaster recovery.

No. Deployment URLs are random and non-sequential, but anyone with the link can access the app unless the app adds authentication and authorization, which are built-in capabilities in the AppDeploy SDK.

AppDeploy handles platform-level isolation and infrastructure controls. You still handle who can sign in, what each user can access, and your app's own privacy and compliance requirements.

Do not put secrets or API keys into prompts or project files.
If your app needs credentials or end-user runtime data, collect and store only the minimum required inside the running app for that workflow.

AppDeploy combines tenant-scoped data paths with infrastructure-level policy enforcement. In practice, storage access, shared database access, and internal service paths are designed to stay within the current app's scope.

AppDeploy uses TLS in transit for communications with the service and encryption at rest for stored data where supported by the underlying infrastructure.

Operational access is intended to be limited to authorized personnel under least-privilege controls for support, security, and reliability purposes.
AppDeploy's platform controls are designed to keep tenant data scoped, but internal operational access is not the same thing as end-user access inside your app.

AppDeploy is currently free under fair use, so you can deploy your first app without a credit card.
We are still early and using this phase to improve reliability, UX, and platform support based on real usage.

We may introduce a paid tier in the future for a subset of services or usage levels, while keeping basic functionality available for free.
We do not have a timeline to share.
If we introduce pricing, it will be competitive with comparable developer infrastructure and deployment services.

No. You retain ownership of the project files and materials you submit ("User Content").
To operate the service, you grant AppDeploy a limited, non-exclusive, worldwide license to host, reproduce, and modify your content only as necessary to build, deploy, and serve your app at a hosted URL.
You can request deletion of your deployments and associated data at any time. After we process deletion, we stop serving the deployment and remove the content from our primary systems.
Backups may be retained for up to 30 days for disaster recovery.

Your app and your User Content remain yours. You keep the rights and economic upside from what you build.
AppDeploy's rights are limited to the operational license needed to run the service.
Your app may include third-party dependencies and services, and those licenses and terms still apply.

No. Uploading or deploying through AppDeploy does not transfer ownership.
You retain ownership, and AppDeploy only receives the limited license needed to host and deploy your app.

You can email us at support@appdeploy.ai and we will do our best to promptly reply and assist.