Softwr

Developer Tools · head to head

Frappe vs Very Good Security

Frappe logo

Frappe

Developer Tools

The Python web framework behind ERPNext, sold as managed hosting through Frappe Cloud

From
Free
Free plan
Yes
Very Good Security logo

Very Good Security

Cybersecurity

Tokenisation proxy that keeps card and personal data out of your own systems and out of PCI scope

From
$1000/month
Free plan
No

The short version

  • Only Frappe has a free tier, so it costs nothing to try first.
  • Each has a real cost: Frappe the framework is strongly opinionated: its own ORM, templating and job queue mean general Python and Django experience transfers only partly, and onboarding a new developer takes weeks rather than days.; Very Good Security vGS sits in the live path of every request carrying sensitive data, so its latency and availability become yours, and an outage in the proxy is a payment outage no matter how healthy your own systems are.
  • They diverge on capability: Frappe covers DocType modelling, Very Good Security covers Aliasing proxy.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Frappe and Very Good Security actually diverge.

Attributes where Frappe and Very Good Security differ
AttributeFrappeVery Good Security
Starting priceFree$1000/month
Pricing modelPer month by site or serverPer month
Free tierYesNo
PlatformsWeb, Linux, DockerWeb, API
CategoryDeveloper ToolsCybersecurity

Identical on both: user rating (Not yet rated).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in Frappe

  • DocType modelling
  • Role and field permissions
  • Built-in REST API
  • Background jobs
  • Bench CLI
  • Frappe Cloud hosting
  • App marketplace
  • Multi-tenancy

Only in Very Good Security

  • Aliasing proxy
  • PCI scope reduction
  • Network tokenisation
  • Processor optionality
  • Card issuing data
  • Vault and access controls
  • Data residency options
  • Compliance artefacts

What people use each for

The jobs each tool is most often brought in to do.

Frappe

  • A team building an internal business application that needs permissions, audit trail and an API on day one rather than in month threenot Very Good Security
  • An ERPNext user who wants managed hosting, automatic updates and offsite backups without hiring a systems administratornot Very Good Security
  • An Indian or emerging-market business that wants to pay for application hosting in local currency at local price pointsnot Very Good Security
  • A consultancy shipping custom vertical apps to clients on a shared framework with per-client site isolationnot Very Good Security

Very Good Security

  • A marketplace facing its first PCI DSS Level 1 assessment that wants to keep card data off its own estate rather than harden a dozen servicesnot Frappe
  • A merchant negotiating with a second acquirer that needs card credentials portable so the negotiation is real rather than theoreticalnot Frappe
  • A fintech collecting bank account and identity documents that wants sensitive fields absent from logs, backups and analytics warehouses by constructionnot Frappe
  • A card issuer that must display a full PAN in its own mobile app without the app or its backend touching cardholder datanot Frappe

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Frappe

  • The framework is strongly opinionated: its own ORM, templating and job queue mean general Python and Django experience transfers only partly, and onboarding a new developer takes weeks rather than days.
  • The developer pool is small and heavily concentrated in India, so hiring Frappe experience elsewhere is slow and expensive relative to mainstream stacks.
  • Documentation is uneven in depth and lags behind releases in places, so real answers often come from reading the source or the community forum.
  • Major version upgrades of the framework have historically broken custom apps that reach past the DocType layer, so bespoke code carries a recurring maintenance cost at each upgrade.
  • Frappe Cloud recommends against its cheapest Hetzner-backed option for mission-critical production, so the headline $5 entry price is not the price of a production-grade deployment.

Very Good Security

  • VGS sits in the live path of every request carrying sensitive data, so its latency and availability become yours, and an outage in the proxy is a payment outage no matter how healthy your own systems are.
  • Token portability is the whole selling point yet leaving VGS means migrating tokens back out, a project the vendor has no incentive to streamline, so the lock-in you removed from your acquirer partly moves to VGS.
  • Entry pricing at around one thousand US dollars a month is real money for a pre-revenue fintech, and it buys volume-limited throughput, so cost scales with exactly the growth that made you buy it.
  • Scope reduction is not scope elimination: your QSA still assesses how you integrate, and teams regularly discover that a support tool or an internal admin screen pulled plaintext back in and dragged systems into scope again.
  • Proxy-based interception constrains how you design request flows, and non-standard payloads, streaming uploads or binary formats often need custom routing rules that make debugging production issues noticeably harder.

Pricing, plan by plan

Frappe

Free
  • Framework, self-hostedFree
    • MIT licensed, no licence fee
    • Install with bench on your own Linux servers
    • You carry updates, backups and security patching
  • Frappe Cloud Sites$5/month
    • Also listed at ₹410 per month
    • Shared servers with 150+ installable apps
    • Automatic updates and offsite backups
  • Frappe Cloud Servers$40/month
    • Also listed at ₹3,600 per month
    • Dedicated or shared virtual machines
    • Unlimited sites on your server

Very Good Security

$1000/month
  • Starter$1000/month
    • Aliasing proxy
    • Vault storage
    • PCI scope reduction
  • Growth$undefined/month
    • Network tokenisation
    • Multiple processors
    • Data residency options
  • Enterprise$undefined/year
    • Custom vault architecture
    • Dedicated support and SLA
    • Contractual compliance coverage

Which should you pick?

Choose Frappe if

  • You need doctype modelling.
  • You want to start without paying.
  • You work on Web, Linux, Docker.
  • You also want role and field permissions.

Choose Very Good Security if

  • You need aliasing proxy.
  • You work on Web, API.
  • You also want pci scope reduction.

Questions people ask

Is Frappe or Very Good Security better?
Neither clearly leads. Frappe starts at Free and Very Good Security at $1000/month, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Frappe or Very Good Security?
Frappe has a free tier; the other does not. Paid plans start at Free for Frappe and $1000/month for Very Good Security.
Does Frappe or Very Good Security run on more platforms?
Frappe runs on Web, Linux, Docker. Very Good Security runs on Web, API.
Can I use Frappe for free?
Yes. Frappe has a free tier, so you can try it without paying. Very Good Security starts at $1000/month.
What is Frappe best used for?
Frappe is most often used for a team building an internal business application that needs permissions, audit trail and an api on day one rather than in month three, an erpnext user who wants managed hosting, automatic updates and offsite backups without hiring a systems administrator, an indian or emerging-market business that wants to pay for application hosting in local currency at local price points, a consultancy shipping custom vertical apps to clients on a shared framework with per-client site isolation. Of those, a team building an internal business application that needs permissions, audit trail and an api on day one rather than in month three and an erpnext user who wants managed hosting, automatic updates and offsite backups without hiring a systems administrator are not what Very Good Security is typically brought in for.
What can Frappe do that Very Good Security cannot?
Frappe covers DocType modelling, Role and field permissions, Built-in REST API, Background jobs. Very Good Security covers Aliasing proxy, PCI scope reduction, Network tokenisation, Processor optionality.

Answered from the vendors’ own pages

Frappe: Is Frappe the same as ERPNext?

No. Frappe is the framework; ERPNext is the ERP application written on it. You can run Frappe without ERPNext to build your own applications.

Very Good Security: Does VGS make me PCI compliant?

No. It removes cardholder data from your systems so your assessment covers a far smaller boundary, but you still complete an assessment and your integration is part of it.

Frappe: What licence is the framework under?

MIT, which is permissive and imposes no obligation to publish your changes, unlike the AGPL used by several open source ERP rivals.

Very Good Security: Can I move to another processor without re-collecting cards?

Yes, that is a core reason people buy it. The vault reveals stored credentials to whichever processor you route to.

Frappe: Can I pay in rupees?

Yes. Frappe Cloud publishes the same plans in Indian rupees, ₹410 a month for sites and ₹3,600 for servers, rather than converting a dollar price at checkout.

Very Good Security: What does it cost?

Published entry pricing is about one thousand US dollars per month; growth and enterprise tiers are quoted.

Frappe: Do I have to use Frappe Cloud?

No, self-hosting with bench or Docker is fully supported and free. Frappe Cloud is a convenience purchase, and it funds the open source work.

Very Good Security: Is it only for card data?

No. The proxy handles any sensitive field, including bank details, national identifiers and documents, though payments is where the product is now focused.

Share

Related pages

Other head to heads