Credits and usage limits

Many providers charge for app creation using credits or message quotas. The raw number of credits tells you little, as each provider calculates consumption differently.

• How many credits are included in the plan?
• How much does a typical request cost?
• Do unused credits expire?
• Can credits be purchased?
• Are failed requests charged?

Credits during ongoing operation

On some platforms credits are only required during creation. Others also charge for AI features, database accesses, automations, or server resources within the finished app.

• Page views and traffic
• Database and API calls
• AI features within the app
• Email sending and automations
• Server and compute time

Code export

Code export determines how independent you remain from the provider. A complete export can enable a later hosting migration or manual further development.

• Frontend and backend code
• Database schema and configuration
• Files, images and dependencies
• Environment variables
• Documentation for local installation

Project ownership

Check what rights you receive to the generated code, design and created content. For client projects it should also be possible to transfer usage rights.

• Commercial use allowed
• Code can be modified
• Resale and transfer to clients possible
• Transparent provisions after termination
• Known timeframes for data deletion

Hosting and publishing

Integrated hosting makes publishing easier. However, check which resources are included and whether a later migration remains possible.

• Hosting and SSL included in the plan
• Custom domain supported
• Storage and traffic limits
• Available server locations
• Export and hosting migration possible

Data protection

During app creation prompts, project information and possibly personal data are processed. For business projects transparent data-protection information is particularly important.

• Company headquarters and server location
• Data transfers outside the EU
• Data processing agreement
• Subcontractors used
• Use of prompts for AI training

Databases and backend

A database is required for user accounts, bookings or stored content. Compare not only features, but also limits, costs and export options.

• Supported database types
• Storage space and record limits
• Backups and restoration
• Data export
• Location and cost of the database

User accounts and authentication

Customer portals, membership areas and internal applications require secure sign-in. A generated login interface alone does not guarantee a secure implementation.

• Registration and password sign-in
• Email confirmation
• Password recovery
• User roles and access rights
• Two-factor authentication

Integrations and interfaces

Integrations connect your app to payment providers, email services, calendars, CRM systems and other external platforms.

• Payment processing
• Email and calendar services
• CRM and support systems
• Cloud storage and external databases
• Own REST or GraphQL APIs

AI models used

Many platforms rely on external AI models. More powerful models can deliver better results, but may also consume more credits or be restricted to higher-tier plans.

• Transparency about the model used
• Model switching possible
• Impact on credit consumption
• Ability to use own API keys
• Data protection at the model provider

Version control and restoration

AI-generated changes do not always achieve the desired result. Therefore older project states should be restorable.

• Automatic version snapshots
• Undo function
• Project history
• GitHub or GitLab integration
• Separate development and production environments

Support and documentation

Even with an AI app builder technical issues can occur. For business projects good support and clear documentation are important.

• Help centre and documentation
• Community forum
• Email or ticket support
• Live chat
• Guaranteed response times

Scalability

A small prototype has different requirements than a public app with many users. Check early whether resources and limits can be expanded later.

• Traffic and user limits
• Scalable database
• Additional compute power
• Costs as usage grows
• Support for multiple environments

Contract term and termination

Compare not only the entry price, but also renewal, notice periods and how apps and data are handled after the contract ends.

• Monthly or annual billing
• Automatic contract renewal
• Cancellation and export period
• Price after promotional periods
• Deletion of apps and data

Define the project idea

Decide which problem the application should solve, who will use it and which core function is required.

Define requirements

List important pages and features and split them into essential and optional components.

Compare AI app builders

Compare credits, code export, hosting, databases, data protection, integrations and prices.

Build your first prototype

Start with a simple version and describe the purpose, target audience, core pages and desired style as concretely as possible.

Add features incrementally

Expand the project incrementally and test each new feature before adding more.

Test the application

Check layout, navigation, forms, user accounts, databases and interfaces on different devices.

Review data protection and security

Review the data processed, external services and required legal texts. Business-critical apps should also undergo a technical review.

Connect a domain and publish

Connect your own domain, enable HTTPS and check all content and features before publishing.

Monitor costs

Monitor credits, database usage, traffic, external services and ongoing AI costs.

Set up exports and backups

Regularly export code and data and use version control so that your project is not stored exclusively in the provider account.