Skip to content

Architecture

A Creator doesn’t need to think about infrastructure day to day, but a few architectural facts explain why certain things in Anybuild work the way they do - particularly around security and where SQL shows up.


Every application gets its own dedicated database - this is true across all plans, including the free trial. What varies by plan is the infrastructure those databases run on:

  • On lower tiers (Trial, Starter, Pro, Scale), applications run on shared infrastructure: a shared PostgreSQL cluster and a shared Node.js application layer, with each application’s data kept in its own separate database on that cluster.
  • On higher tiers (Business, Advanced, Enterprise), applications run on dedicated, reserved infrastructure - a cluster and runtime not shared with other customers.

In both cases, one application’s data is never stored in the same database as another’s. This is a meaningfully different model from typical multi-tenant SaaS platforms (e.g. Salesforce), where many customers’ records commonly live side by side in the same shared database, distinguished only by a tenant ID. It’s part of why Anybuild’s default security posture starts from a stronger position than most SaaS systems.


Anybuild is built on PostgreSQL - widely regarded as the most capable open-source database, and enterprise-grade in the same category as Oracle or SQL Server in terms of the volumes it can handle. It’s also the database most compliant with the SQL standard, with a rich type system and a deep library of built-in functions (window functions among them).

This matters for day-to-day Creator work because SQL is not hidden away inside the platform - it’s exposed directly wherever it’s useful: field expressions, Stored and Virtual Calculations, Views, and Server Functions all use real SQL rather than a proprietary abstraction layer.


The server runtime is Node.js - a JavaScript runtime built on Chrome’s V8 engine, fast enough to run business logic at the server level. Because Node.js has access to the NPM ecosystem (millions of open-source packages), the platform - and Server Functions written by Creators - can pull in ready-made functionality and integrations rather than building everything from scratch.


Anybuild applications support thousands of concurrent users against the same database. From a single device, it’s common to open multiple sessions in separate browser tabs - useful if one session is busy (e.g. mid-edit on an Entity) and you want to keep working in parallel.