Bigcapital

The documentation recommends at least 2 CPU cores and 4 GB of RAM, which supports up to 10 organizations, plus 5 to 10 GB of storage for the MariaDB database. The production Docker Compose stack runs the web app, the API server, MySQL/MariaDB, MongoDB, Redis, and an Nginx gateway, and serves the app on port 8000. An automated setup script is available if you do not want to configure the stack by hand.

Yes. Each organization has a base currency, and you can add other currencies through the currencies settings for multi-currency accounting. The branches feature lets you create branches, mark one as primary, and activate or deactivate them, with branch data available through the API.

Bigcapital connects to banks through Plaid. On a self-hosted instance you supply your own Plaid credentials and webhook configuration through environment variables. Once connected, transactions sync into bank accounts, where you can categorize them, match them to existing records, create bank rules, and reconcile the account. Syncing can be paused, resumed, or refreshed per account.

Yes. The documented REST API covers accounts, customers, vendors, sale invoices, bills, expenses, inventory, banking, roles, and financial reports, and is intended for headless accounting integrations. Requests authenticate with an API key prefixed with bc_ or a JWT token; with a JWT you also pass an organization-id header. A Postman workspace is linked from the README.

Yes. Items can be organized into categories and tracked across multiple warehouses, with inventory adjustments, warehouse transfers, landed cost allocation, and inventory valuation reports. Item, warehouse, and inventory cost endpoints are part of the public API.