The install should feel managed, not improvised.

CreditSoft is packaged around the stack a real office needs: PostgreSQL data, PHP 8.5, OPcache, queues, local routing, container services, and controlled public callback paths.

Installation stack

Managed Tech Stack

The point is not making owners become system administrators. The point is that CreditSoft can be installed, updated, backed up, and connected as a business system when access is provided.

  • PostgreSQL gives the intranet a stronger base for multi-node, CRM, billing, and reporting workloads.
  • PHP 8.5 and OPcache are part of the expected runtime direction for the office stack.
  • Dockerized services give the installer a repeatable path for intranet, queue, scheduler, router, database, and CRM sidecar pieces.
CreditSoft settings screen
Managed Tech Stack Current product view from the CreditSoft workspace.

Core runtime

  • PostgreSQL The data layer is aimed at stronger multi-node and reporting behavior than local file databases.
  • PHP 8.5 The server runtime should match the modern PHP direction with OPcache enabled.
  • Queues and scheduler Background sync, email prep, backups, and automation need workers, not fragile page-load hacks.

Managed installation

  • Container services The office stack groups intranet, router, queue, scheduler, database, and CRM services.
  • Public bridge Website callbacks and portal traffic use approved public routes without exposing private casework.
  • Supportable setup The installer should make repeatable choices so AnyDesk-style installs do not depend on AI help.

Keep the overview clean.

This page holds the technical setup detail so the features page can stay a clean buyer overview.