FormLogic

What is FormLogic?

FormLogic brings the interface, records and automation of a business application into the same workspace. A form defines the information you collect. Apps organise that information into screens and tools. Flows connect a submission or an event to the work that follows. You can start with a simple public form and develop it into a staff workspace, a customer portal or a more specialised operational application.

The platform is designed for teams that need their own workflow rather than another disconnected spreadsheet. Forms, linked records, dashboards, reports, members and roles can be assembled visually. Developers can extend the result with private backend logic, custom interfaces and external integrations. Manual building does not require an AI provider.

Build the workspace around the work

The form builder supports validation, conditional logic, linked records, uploads, signatures, calculated values and server-side submission logic. A form is more than a screen: it supplies a reusable data model that can be shared between apps. Changing the experience does not have to mean creating a second copy of the records.

App Studio brings navigation, branding, dashboards and role-aware views together. KPI cards, charts, tables, record lists and reports can describe the same underlying activity from different perspectives. Marketplace starters provide an editable starting point for areas such as field service, hospitality, inventory and front-desk operations.

• Create public forms and internal record-entry tools.
• Give customers and staff different portals over shared forms.
• Compose dashboards and printable reports from existing records.
• Install and customise business app packs rather than rebuilding every workflow.
• Trigger visual flows from submissions, database events and connected devices.

Host an editable application with a private backend

FormLogic can host SoftN applications alongside its form-centred workspaces. The embedded Visual Builder and AI Studio let an owner work on a portable app without leaving the platform. Editable .ui and .logic source stays available, while private server routes and SQLite migrations describe the hosted backend.

The owner can inspect and administer the app database through record controls. Those controls enforce database constraints, but they do not invoke every validation function in an app’s backend. Business-critical changes should use the app’s intended workflow when those rules matter. Publishing a draft preserves existing records; editor previews do not execute the hosted backend.

Client exports, full project downloads and database backups have different purposes. A downloadable client is not an offline copy of an authenticated service. Project downloads exclude live database records and server credentials. Operators need a separate, consistent backup plan for hosted app databases.

Where FormLogic fits in the ecosystem

FormLogic owns the hosted business records, access control, app configuration and operational workflows. SoftN supplies portable interfaces and editing tools. ZIPP supplies execution for form and app logic through the relevant sandbox and host integration. These roles are connected, but they are not interchangeable.

OAIY is optional. Pair it when a workflow needs models or services on a local computer, device plugins or background execution. Aokie is an OAIY-managed phone plugin that can deliver call, transcript and message events into a FormLogic application. The optional native app shell in the FormLogic repository is not the OAIY desktop runtime.

FormLogic installs its hosted SoftN runtime, embedded editors and native backend modules from a verified SoftN release. The integration checks the release identity, file digests, engine bytes and protocol compatibility. A release run freezes that selection so separate jobs do not silently build against different upstream releases.

A practical starting point for connected operations

An illustrative service business can use one form-backed data model for customers, jobs and visits. Customers submit requests through a portal, staff manage the queue, and an administrator reviews performance. A form event can start a flow that prepares a notification or creates a follow-up record. This is a design example, not a claim about an existing customer deployment.

A more specialised application can bring its own SoftN interface and private SQLite backend. That path is useful when the interaction is larger than a conventional form. It still requires deliberate access rules, reviewed migrations and tests for the actual business process.

Choose your deployment and AI connection

Explore the hosted demo before installing anything. For self-hosting, follow the repository’s developer and deployment guides. The platform uses a PHP/Slim backend, MySQL platform metadata and SQLite for form or hosted-app data. Node is needed for frontend builds and for the native hosted-app backend path, not only for development.

Bring-your-own AI is optional. OAIY can connect local models and provider services, while supported direct providers and scoped external AI integrations offer other paths. Providers may charge separately. Keep OAIY running when a connected feature depends on its local services.

FormLogic is source-available, not open source. Its licence permits free self-hosting and internal business use, subject to its terms. Reselling the software or charging others for a hosted or managed FormLogic service requires a separate agreement. Review the actual licence before planning a commercial offering.