Everything in one place, so it can talk to itself.
Most small operations run on four or five tools that don't know about each other. The point of MFICore is that the form, the database, the page and the automation are the same system, so wiring them together is a choice rather than a project.
Websites
A tree of pages edited in the browser. Every save is a version you can go back to, and publishing is a separate step, so a draft is never live by accident. Bring your own domain or use one of ours — either way the certificate is issued and renewed without you thinking about it. You can define your own reusable blocks, and your own header and footer.
Data
Tables with a schema, stored as JSON but queryable as real SQL columns. Read them in a console, save the query as a view, and drop that view onto a page as a live table or a chart. Reads run sandboxed against a role that can only read.
Forms
Typed fields including image and video capture. Public, or restricted to people who have signed in. A submission is stored, and can trigger a workflow — which is where a contact form stops being a mailbox and starts being a process.
Automation
A visual builder: conditions, loops, parallel branches. Nodes for HTTP calls, email, your datastore, a local language model, scripting in C# or JavaScript, and a set of connectors for things like IMAP and calendars. Triggered manually, on a schedule, by a form, or by an incoming request.
Accounts and access
Every site is its own OpenID Connect provider, so other software can use it to sign people in. Access to the dashboard is per-feature and can be handed to a team without handing over the whole site.
See the whole thing for the price of a coffee.
Or read exactly what each part costs first.