DeplAI
— credits
DeplAI

Application

Dashboard

HomeYour ProfileOrganizationsUsageDocumentation

Services

DeplAI AgentPreviewUI/UX customizerSecurity AgentDASTCloudDeployInstance ManagementCode ReviewerSoonSessions

BYOK

KeysCatalogCompareUsage

Account

BillingInvoicesCreditsRefer & EarnNEWIntegrations
Settings
— creditsFree
deplaiDocumentation

Getting Started

Building Applications

Working With Your Application

Improving an Application

Application Quality

Projects and History

Troubleshooting

FAQ and Reference

Account and Governance

FAQ and Reference

Frequently Asked Questions and Glossary

This page answers the most common questions about DeplAI and provides a clear definition of key product terms.

This page answers the most common questions about DeplAI and provides a clear definition of key product terms.

---

Frequently Asked Questions

What is DeplAI?

DeplAI is an autonomous application builder. You describe the application you want in natural language. DeplAI creates the application, runs it, evaluates the working result, automatically improves issues it discovers, and gives you an interactive preview and the generated source code.

What can I build?

You can build full product applications: online stores, appointment booking platforms, project management dashboards, customer portals, inventory managers, internal tools, and membership systems. Any application with pages, user workflows, structured data, and role-based access is a great fit.

Do I need to choose a programming framework?

No. The core product principle of DeplAI is: The user chooses the product; DeplAI manages the implementation.

You describe who uses the application, what they should accomplish, what information is saved, and how it should feel. You do not need to choose a frontend framework, backend library, database tool, or authentication system. DeplAI makes and manages those implementation choices for you.

When can I see my application?

You can see your application as soon as the status indicates Preview available. This happens once DeplAI successfully starts the application. You do not have to wait for every background evaluation or quality check to finish before you open and explore the preview.

What is the difference between Preview Available and Ready?

  • Preview available means the application is running and interactive. You can open it in the preview panel, click buttons, submit forms, and navigate screens.
  • Ready means DeplAI has also completed all its required application checks successfully (verifying key user journeys, checking layout on desktop and mobile, and confirming that the running application matches the saved version). Ready is the point where you can start a Modify request to build on that finished version.

Does DeplAI test the application automatically?

Yes. DeplAI does not just generate static files; it starts the application and actively tests it. DeplAI exercises important user flows (such as signing in, adding items to a cart, or booking an appointment), checks screen presentation on desktop and mobile viewports, and verifies that navigation and data actions behave correctly.

Can DeplAI improve problems it finds?

Yes. DeplAI features a self-healing build process. When automated checks detect a material problem—such as a broken form, an unhandled user action, or an obvious layout defect—DeplAI automatically updates the application, saves a new version, restarts the preview, and verifies the result again.

Can I request changes after the application is built?

Yes. Once an application reaches Ready, you can use Modify in the conversation to request changes in natural language (for example, *"Add a filter for product categories and make the header dark"*). DeplAI modifies the existing application rather than starting from scratch.

What happens to previous versions?

Previous versions remain permanently preserved in your conversation history. Whenever DeplAI modifies an application or repairs an issue, it creates a new saved version rather than overwriting your past work. You can select any earlier version from history to inspect its source code, compare changes, or download the codebase.

Does modifying an app overwrite the previous version?

No. Modifying an application creates a new saved version. Your previous versions remain fully intact in the conversation history. You can switch back to view earlier versions, inspect their files, or download their code at any time.

What is Retry?

Retry starts a fresh build attempt from your existing accepted product request. Use Retry when a build failed or was interrupted, and you want DeplAI to attempt the build again from scratch without using any code from the failed attempt.

What is Ask DeplAI to fix?

Ask DeplAI to fix (also called Fix) uses an unsuccessful build and its recorded failure details as the starting point. Use Fix when DeplAI created the application but a check or workflow failed, and you want DeplAI to continue repairing that specific build.

Can I inspect the generated code?

Yes. Open the Files panel in the inspector to browse the complete source code generated for the selected application version. You can open any file to read its contents and view its structure.

Can I compare application versions?

Yes. On the Files panel, when multiple versions have been saved during builds or modifications, you can use Diff to compare changes between versions. Files added or modified are clearly marked.

Can I download the codebase?

Yes. On the Files panel, click Download code to download a clean archive of the generated source for the selected version. The archive contains the source files necessary to run and develop the application outside DeplAI, free of temporary build caches or runtime secrets.

What happens if a build fails?

If a build fails, DeplAI updates the status to Needs attention or Build failed and records the activity and check outcomes in the Logs and Checks panels. Your conversation and previous saved versions remain safe. You can click Ask DeplAI to fix to repair the issue, click Retry to start fresh, or update your request.

What happens to my files after a temporary build finishes?

Your saved application source is stored independently from temporary build and preview runtimes. When a temporary preview environment stops, your saved application versions, files, logs, and checks remain permanently preserved in your conversation for inspection and download.

Does preview data become production data?

No. Preview applications often include generated demonstration data (such as sample products, example tasks, or mock customer records) so that you can interact with a populated, realistic product. Demonstration data exists strictly for preview and testing. When you take your application to production outside DeplAI, you connect your own live data.

Can I deploy directly from DeplAI?

The current DeplAI application builder focuses on building, previewing, improving, and exporting your application. It does not deploy your generated application to external production hosting or custom domains. You download the generated codebase and deploy it to your chosen hosting provider.

*(Note: Workspace services for connecting an existing GitHub repository or ZIP project and planning AWS infrastructure with Terraform remain available separately in the workspace.)*

---

Glossary of Product Terms

TermDefinition
ApplicationThe software product created by DeplAI based on your natural language request.
ProjectA workspace boundary that groups connected repositories, ZIP uploads, or application threads.
ConversationA product development thread in DeplAI holding your requests, follow-up answers, builds, and versions.
BuildA single execution attempt to create, retry, fix, or modify an application.
Application versionA saved source snapshot preserved at key milestones or after repairs (also labeled as a revision).
PreviewThe live, running instance of an application version that you can interact with in your browser.
Preview availableStatus indicating the application is running and accessible in the preview panel.
ReadyStatus indicating all required application checks and user journey evaluations passed successfully.
Needs attentionStatus indicating the build halted or a required check failed and requires user action.
ChecksAutomated product-level verification steps evaluating start-up, user journeys, and presentation.
ActivityReal-time operational progress updates displayed in the Logs panel.
FilesThe inspector panel where you can browse and inspect the generated source tree for a version.
Download codeThe action to export a clean archive of your application source code.
RetryAn action that launches a new build attempt from the accepted product request.
FixAn action that instructs DeplAI to repair a failed build using its recorded error details.
ModifyAn action that applies a new change request to an existing Ready application version.

Related: What is DeplAI? | Create your first application | Troubleshooting

On this page

Frequently Asked QuestionsWhat is DeplAI?What can I build?Do I need to choose a programming framework?When can I see my application?What is the difference between Preview Available and Ready?Does DeplAI test the application automatically?Can DeplAI improve problems it finds?Can I request changes after the application is built?What happens to previous versions?Does modifying an app overwrite the previous version?What is Retry?What is Ask DeplAI to fix?Can I inspect the generated code?Can I compare application versions?Can I download the codebase?What happens if a build fails?What happens to my files after a temporary build finishes?Does preview data become production data?Can I deploy directly from DeplAI?Glossary of Product Terms