Memory and CPU Planning
Plan AutoCore CPU and memory allocation without turning a rehearsal size into an unsupported capacity guarantee.
No fixed minimum RAM, CPU count, user capacity, or listing capacity is enforced by the current installer source. Plan resources by workload and topology instead of copying a rehearsal host size.
Allocation considerations
Account for the API and worker processes, two Next.js application surfaces, PostgreSQL, Redis, Meilisearch, image processing, backups, and the container runtime. Leave headroom for migrations, temporary database dumps, media variants, and search reindexing.
Verification
Record the planned allocation, run the package preflight, and validate service health under the intended workload before acceptance. A passing installer preflight does not prove performance capacity.