Guidance on Self-Hosting Frappe Cloud Without Press CLI

Frappe Cloud
, , ,
1

Hi everyone,

I am currently working on setting up a self-hosted Frappe Cloud deployment with separate servers for the app, database, and proxy, but without using press or a Frappe Cloud subscription.

Most of the documentation I have found is related to either:

  1. Local development setup (which uses bench and press CLI).
  2. Frappe Cloud-managed hosting, which requires a subscription.

However, I want to self-host everything while keeping full control over my infrastructure.

My planned setup:

  • Proxy Server (Reverse Proxy) – running NGINX
  • App Server (Frappe Application)
  • Database Server (MariaDB)

I would like to know:

  1. Is there an official guide or community-supported documentation for self-hosting Frappe without press?
  2. How do others in the community deploy Frappe in production with a multi-server setup?
  3. Are there any best practices or potential issues I should be aware of when setting this up manually?

Any guidance, documentation links, or suggestions would be greatly appreciated! :blush:

2

Frappe/Press and Frappe/Agent is required if you are hosting your own frappecloud like setup. Are you planning to setup such service so you can charge subscriptions for your customers? Your customers can manage their benches, sites etc? You “also” want to start your customcloud?

If you just need a setup for your own or have frappe application that you need to host then use

Progressive approach

1 Like
3

Does anyone have an AWS scaleable environment for frappe press? Terraformed or manual architecture. we have an industry-specific cloud we are doing.