How the core works

PHOENIX Cloud has three parts. You only ever use the second one, your site; the other two work behind it.

The parts

Part	What it does
Hub (cloud.phnxtech.com)	The demo, sign-in, plans and billing. It keeps the list of customer sites and asks for new ones to be set up.
Your site	Your own copy of the software with its own database, its own database user and its own files. ERPNext, your system (for example Sourcing Management), your website and your brand all run here.
Set-up agent	An internal service that does a fixed list of jobs on customer sites: create a site, install apps, apply branding, create the first user, back up, suspend, resume and archive. Only the Hub can reach it; it has no public address.

Every site is served over HTTPS. The certificate is issued automatically, and only for addresses the Hub confirms belong to a real customer site.

What happens when a site is ordered

1. We create your company in the Hub and start the set-up.
2. The set-up agent creates your site and its database. This takes a few minutes; demo sites come from a ready spare and open in about a minute.
3. The apps of your plan are installed: ERPNext, your system and the website and branding apps.
4. Your system’s defaults are applied: the modules you need, the workspace and your letter head.
5. Your brand is applied: your settings first, then your reseller’s, then the PHOENIX defaults.
6. Your first user is created as System Manager (not the built-in Administrator).
7. Your website is set up with your company name, with no demo banner and no PHOENIX credit.
8. Your site becomes Active and you receive a welcome email with a link to set your password.

Every job and every step is written to a provisioning log, so we can see exactly what happened on each site.

Life of a site

State	Meaning
Provisioning	Being set up
Active	In use
Suspended	Switched off for a while, data kept
Archived	Closed and taken off the server

Why it is built this way

• Isolation: one database per company keeps your data apart from everyone else’s.
• Repeatability: every site is set up by the same steps, so every site behaves the same.
• A small attack surface: the agent that can change sites cannot be reached from the internet and can only do its fixed jobs.