Deployment
A project with a shape, not a subscription with a form
HerbaPortal is not a SaaS product: the system runs on your infrastructure and you own your copy outright — nothing is cloud-based. There is no public price list and no self-signup: every deployment starts with a conversation about how your shop works today, and ends with an instance adapted to it. And if you need it, we will build and manage the infrastructure for you — on your own servers, if that is what you prefer.
How a project runs
- 1
Discovery
How does an order reach you today? Who converts formulas to grams and prices? What ERP, couriers, payment methods? Which modules matter — settlements, loyalty? What language and currency?
- 2
A written offer with a scope
The base product plus named customizations plus your hosting variant. The scope is on paper; anything outside it is an amendment, not an argument.
- 3
A 30 / 40 / 30 contract
30% at signing. 40% when you accept the work on your trial instance. 30% after production go-live. Payment follows progress — you see your shop working before the second installment.
- 4
Maintenance, if you want it
A separate monthly agreement, scoped to your hosting variant.
The pilot: your shop, not a demo
Send us a CSV export of your catalog and we'll stand up a trial instance with your actual products, your currency, your VAT rates. You evaluate your own shop. The pilot is free, non-binding — and time-boxed, because a trial without an end date is an eternal “we're still thinking”.
Two hosting variants — your call
Whichever variant you choose, one thing never changes: this is not SaaS. The instance is yours. If you want everything on your own infrastructure — your server or your own cloud account — we will build and run it there for you. Nothing ever sits on a shared VPS.
A. Managed — we run it for you
- It can run on your own infrastructure — your server or your own cloud account — or on one we provision for you alone. Never a shared VPS.
- You provide: a domain (one DNS record).
- Backups: nightly, to S3 — we watch them and rehearse restores.
- Updates: ours, one client at a time, with rollback.
- A 3 a.m. outage: our problem.
- Isolation: your own database and a user with rights to it alone — tested as part of the provisioning procedure.
- For: shops without their own IT; the fastest start.
B. Your own server
- You provide: a VPS, domain and DNS, S3 buckets, SMTP, payment keys.
- Backups: the same mechanism; the rehearsal discipline is yours (or part of a maintenance agreement).
- Updates: you, with the manual — or us, under maintenance.
- A 3 a.m. outage: yours (or per the maintenance agreement).
- Isolation: complete — a physically separate machine.
- For: shops with an IT team, or a hard “data stays with us” requirement.
In both variants the installation adjoins what already runs on the machine — it joins an existing proxy and database rather than demanding a clean server.
Operations you can hold us to
Backups with a drilled restore
Nightly per-database dumps to your S3 bucket, 30-day retention. The restore is rehearsed, and the restore script counts documents afterwards — because a restore tool can exit “success” having restored nothing.
Upgrades that cannot half-apply
One command. Migrations must finish cleanly before the new version is allowed to start; rollback is returning to the previous version.
A blast radius of one
Every client is a separate instance. A bad release can reach at most one shop — that is the point of the single-tenant model.
An admin manual written for the owner
Twelve chapters written for the person who runs the shop, not for an integrator. In English today; a translation is a known, priceable piece of work.
A standing security document
With a permission matrix per endpoint and role — and a table of consciously accepted risks. We hand it to your IT person instead of summarizing it.
Your data, your exit
The database is yours in every variant. Nightly backups land in your own S3 bucket, the catalog exports to CSV, patient data exports per patient. If we part ways under managed hosting, you receive a complete database dump and your files. No one is held hostage by their data.
Customization extends — it never forks
A new ERP adapter, a payment provider, a UI language, a pickup-point widget, accounting exports for your bookkeeper: all of it plugs in through adapters and configuration. We won't sell you a fork, because a fork is the system nobody can update two years later — that is exactly what we're protecting you from. One core for all clients is what keeps updates cheap and the maintenance fee low.
See your own shop in it, not a demo
Send us a CSV export of your catalog and we'll set up a trial instance with your actual products — your currency, your VAT rates. Or ask for access to the live demo and start a conversation.