Answers to common questions about building and running with Apexor

Core application configuration is designed to be handled visually. More advanced integrations and custom business logic may require technical knowledge or developer support.

The Mini CRM is intended to help businesses manage customer accounts, order history, roles, basic communication and operational information within the same connected system.

Yes. Applications can provide different experiences for customers, cooks, couriers, managers, administrators and other configured roles.

A cloneable solution is a prepared system project that can be copied into a customer's workspace and used as a starting point for a real business application.

Yes. Customers can adapt branding, screens, widgets, workflows, roles and available functionality while the protected system foundation remains controlled.

The initial food-focused solutions include Restaurant, Café, Home Kitchen and Delivery Kitchen. Additional industries may be added later.

Access to paid capabilities is provided through subscription plans. Available functionality, billing periods and applicable limits are displayed before purchase.

The platform is intended to support plan changes as business needs grow. The exact upgrade and downgrade rules will be shown in the billing area.

Subscriptions can be cancelled according to the billing conditions shown during purchase. Access may continue until the end of the already paid billing period.

Subscription payments are expected to be processed through Stripe or another supported payment provider. Apexor does not normally store complete payment card details.

Apexor is designed around generated Flutter applications and may support web, PWA, Android and iOS publishing workflows depending on the selected plan and project configuration.

Yes. Browser-based preview and hot-reload workflows allow customers to review application structure, content and visual changes before publication.

Publishing workflows are being structured to assist with preparing and delivering generated applications. Apple, Google and other third-party account requirements may still apply.

Apexor uses reasonable technical and organizational safeguards, including controlled access, authentication, encrypted connections and cloud infrastructure.

The customer operating the application determines what end-user data is collected and how it is used. That customer is responsible for its privacy notices, permissions and legal obligations.

No. Apexor provides the technology platform and is not the seller, merchant or contracting party in transactions between a customer and the end users of that customer's application.