Overview & architecture

This section is for developers connecting to a Bizinly workspace, or automating it — as opposed to the rest of these docs, which are written for the people using the app day to day. It stays high-level on purpose: the shape of the platform, not internal implementation.

One platform, modular features

Bizinly's core — customers, contacts, products, quotes, orders and invoices — is always there. On top of that, features are modules a workspace can turn on or off: a sales pipeline for deals and leads, purchasing (purchase orders and suppliers), contracts with online signing, and a scheduler for bookings and appointments. Further capabilities (inventory, projects, and more) are added to the platform over time the same way.

What a person sees inside a given module is still governed by their own role and permissions — a module being on for the business does not mean everyone in it can use every part of it.

Isolated workspaces

Every business's data — its documents, customers, products and settings — is fully isolated from every other business on Bizinly, whether it is on a shared installation or a dedicated one of its own. Nothing about one workspace's configuration or content is visible from another.

Everything is audited

Every write in Bizinly — whatever triggered it: a person clicking a button, an automation, or an API call — goes through the same path: a permission check, validation, the write itself, and an entry in that workspace's activity log. That is true for the API described in Connect with MCP as much as it is for the app's own screens — there is no separate, less-checked path for integrations.

Building on the platform

Modules are one way Bizinly grows. The other two are covered in their own articles:

• The starter project — a ready-to-run SaaS project, with accounts, billing and admin already built, that connects to a Bizinly installation or stands on its own.
• Bizinly Admin — the control plane for anyone running more than one Bizinly installation: people, tenants, modules and audit, in one place.
• Plugins — how a feature is added to Bizinly, or to a starter project, without forking the app.

Where to go next

• Connect with MCP — read and write a workspace's data from your own tools or AI assistant.
• Import & export formats — the CSV/JSON shape for customers and products.
• Document & e-mail placeholders — the token vocabulary used in printed documents and e-mails.
• Contract placeholders — the same, for contract templates.
• Localization — the languages Bizinly speaks, and how a document's own language is decided.

Looking to go deeper than these docs cover — a custom integration, a dedicated deployment, or something not listed here? Book a live demo and talk to us directly.