System Requirements · v1.0

LedgerFlow

Infrastructure, deployment, scalability, security, and operational requirements for LedgerFlow SaaS and on-premise deployments.

Deployment Models
SaaS + On-Premise
Target Scale
1000+ Tenants
Uptime SLA
99.9%
Data Regions
IN, UAE, Global
01

Deployment Architecture

LedgerFlow supports both SaaS (cloud-hosted) and on-premise deployments from a single codebase. Multi-tenancy is achieved via row-level security or schema isolation for large tenants.

Deployment Models

ModelDescriptionTenancyScaling
SaaS (Default)Cloud-hosted, fully managedShared database with row-level isolationHorizontal (stateless API, read replicas)
Dedicated SaaSLarge tenant on separate infraDedicated database schema or instanceVertical + horizontal scaling
On-PremiseSelf-hosted, customer-managedSingle-tenant or private multi-tenantCustomer-controlled

SaaS Infrastructure

Kubernetes Deployment

  • Namespace per tenant: Logical isolation, dedicated resources for large tenants
  • Pod Autoscaling: HPA based on CPU (80%), memory (70%), or custom metrics
  • Node Autoscaling: Cluster autoscaler to add/remove nodes based on pod demand
  • Rolling updates: Zero-downtime deployments with health checks and canary releases
  • Secrets management: HashiCorp Vault or cloud-native secret stores (AWS Secrets Manager, Azure Keyvault)
  • Persistent Volumes: For temporary worker storage; ephemeral for replicated state

On-Premise Deployment

02

Database & Data

Database Technology: PostgreSQL

Data Model Sizing

EntityTypical GrowthIndex Strategy
Vouchers (annual)10K-50K per small companyIndex on date, type, status, company_id
Ledger Entries (annual)50K-200K per companyComposite (company_id, ledger_id, date)
Stock Movements5K-20K per yearIndex on item_id, godown_id, date
Audit Log (annual)200K-500K eventsPartition by month on created_at
Query Performance

Standard reports (P&L, Balance Sheet) for a year of data must complete in under 3 seconds. Use materialized views for common aggregations; invalidate nightly or on key posting events.

Backup & Disaster Recovery

03

Scalability & Performance

Horizontal Scalability

ComponentScaling MethodLimit/Notes
API ServersKubernetes HPA (CPU/memory-based)Min 3, max 100 replicas per phase
Worker NodesSeparate worker pods, job queue-basedScale independently of API
Database Read ReplicasStream replication; manual promotionUp to 10 replicas; route reports to read replicas
Cache (Redis)Cluster mode or sentinel HASeparate cache per large tenant if needed
Object StorageS3/GCS auto-scalingUnlimited; object lifecycle policies for archives

Performance Targets

Load Testing Requirements

04

Security & Compliance

Encryption

Authentication & Authorization

Compliance Standards

Vulnerability Management

Data Residency & Sovereignty

05

Operational Requirements

Availability & SLA

Monitoring & Observability

Capacity Planning

Disaster Recovery

06

Integration Points

Email & Communication

Government Portals & APIs

Third-Party Integrations

07

Localization & Globalization

Language Support

Number & Date Formatting

Tax Localization