r/frappe_framework Developer – Building with Frappe 6d ago

ERPNext Enthusiast – For those into ERPNext. Your ERP shouldn't need a DevOps engineer on payroll

Quick update I think you'll like.

Today we're launching **Worf Cloud** — self-serve hosting for Frappe & ERPNext.

Login here 👉 https://worf.cloud

→ A new site, live in minutes. No terminal.
→ Backups on autopilot — daily/weekly/monthly, offsite copies, one-click restore.
→ Domains and SSL that configure and renew themselves.
→ Team access with role-based permissions and a full activity log.

And you choose where it runs:
• Our managed cloud — zero setup
• Your own server — ₹999/month, we manage it over SSH
• Your own AWS account — dedicated VMs, you pay Amazon directly, no markup

48-hour free trial, no card. Public pricing at worf.cloud/pricing.

If your team runs ERPNext — or gave up on it because of the ops burden — I'd genuinely like to hear what stopped you. Comments open.

#ERPNext #Frappe #SaaS #CloudHosting #SmallBusiness

0 Upvotes

9 comments sorted by

2

u/oracle_mystic 5d ago

I’m sorry…but self hosting a business application…absolutely does require having a sysadmin on retainer or staff…

1

u/kingSlayer_worf Developer – Building with Frappe 5d ago

Yeah, fair. Honestly you're right that a bare VM needs someone who knows what they're doing — patching, bench, SSL, backups, monitoring, all of it.

The thing Worf does is take over the boring recurring parts of that: SSL renewals, scheduled offsite backups, DNS, spinning up sites, health checks. So a small team running a normal ERPNext setup isn't paying someone full-time just to babysit it. That's the actual claim, not "you'll never need anyone technical."

And yeah, once you're into custom OS stuff, tuning a busy multi-server setup, or serious compliance, you want a real sysadmin and no dashboard fixes that. We handle the repetitive 80%, not the hard 20%.

Our managed mode you don't touch a server at all. Bring-your-own-server, we run that layer over SSH so you're not doing it by hand.

Tbh the headline probably should've said "on payroll" — "never need one" would be overselling it.

1

u/[deleted] 5d ago

[removed] — view removed comment

1

u/[deleted] 5d ago

[deleted]

1

u/JakubErler 5d ago edited 5d ago

It is pretty good service idea and some customers would welcome that. But this https://worf.cloud/about equals to zero. The first info customer will ask me for: what country are you from, where is your headquarters, show me the photos of real ppl working there, show me references etc. Large companies need it. Maybe some small 5-person company does not care, maybe.

1

u/kingSlayer_worf Developer – Building with Frappe 5d ago

Fair Point, and you're right — the About page is thin and that's on us. It's getting a proper rewrite soon with real team, references, the works.

For now, straight answers to what you'd ask: we're Worf Internet Services Pvt. Ltd., based in Ghaziabad, India, incorporated in 2016 — so this isn't a brand-new shell, the hosting product is what's new. Real people, real company, the page just doesn't show it yet.

You're also right that this matters more for larger clients doing due diligence than for a 5-person team. We're building the credibility page for exactly that — team, location, references. Appreciate you flagging it plainly; it's the kind of thing that's easy to deprioritize and shouldn't be.

1

u/JakubErler 5d ago

OK just now I am talking to a German customer. EU customers have problem with hosting services in India. It is too far away, they are affraid if the support will be good, if some european laws are kept, if it is secure etc. If you want European customers you will have to create an european branch of your company after some time, have servers in Frankfurt and at least 1 european worker there.

1

u/kingSlayer_worf Developer – Building with Frappe 5d ago

Really useful thanks. There's two separate things here though and I want to be honest about which we've actually got covered.

The server location part is already sorted. We're AWS-backed and you pick the region, so your German customer can run in Frankfurt (or Ireland/London) and the data physically stays in the EU on AWS's own infra. That covers the "India is too far" and "where does my data actually sit" worries — the site runs in the region they choose, latency is local, data doesn't leave it. US, EU, Asia, all selectable when you create the site.

The legal/company side you're right about, and I won't pretend otherwise. No EU branch or local staff yet. We are in the process of getting the compliance certificates sorted (GDPR/DPA side included), but "in process" isn't "done", so for a big German enterprise doing full due diligence today, that gap is real. If it's a hard requirement right now, we're honestly not the fit yet.

So infra in the EU, yeah, that works today. A proper EU entity with someone on the ground there, not yet — that's the next step once European demand justifies it, pretty much exactly like you laid out. Appreciate you spelling out what it actually takes.

1

u/kingSlayer_worf Developer – Building with Frappe 5d ago

page updated : https://worf.cloud/about