Moving Towards a Cloud-Vendor Independent Codebase

[harshvardhan-yc]

🧭 Context

As an open-source company, it is important that our core products remain cloud-vendor neutral and do not enforce tight coupling with a specific infrastructure provider. This ensures broader adoption, easier self-hosting, and long-term sustainability.

At present, our PMS codebase has strong dependencies on AWS services, which limits flexibility for users who prefer alternative cloud providers or on-prem deployments.

❗ Problem Statement

• The current PMS implementation is highly dependent on AWS-specific services
• This creates:
  • Vendor lock-in
  • Reduced flexibility for self-hosted or multi-cloud users
  • Barriers for contributors who do not use AWS
• This is misaligned with the expectations of an open-source ecosystem

💡 Proposed Direction

• We should work towards a cloud-vendor independent version of PMS, where:
• Core logic is decoupled from cloud-specific services
• Cloud integrations are implemented as optional adapters or plugins
  • The system can run on:
  • AWS
  • Other cloud providers

At the same time, we can still support a fully integrated, cost-efficient cloud setup for users who prefer a managed or optimized experience.

🚀 Next Steps

• Audit current AWS dependencies in the codebase
• Identify core vs cloud-specific responsibilities
• Propose an abstraction/interface layer for infrastructure services
• Define guidelines for adding future cloud provider integrations