Certificate valid, renews automatically
Encrypted on the way
Every connection to your system is over HTTPS, so what passes between your team and your system can't be read on the way. The certificate renews itself before it expires.
The plain answers an owner deserves before trusting anyone with the company's books — without jargon, and without promises we can't keep.
Your system and its backups stay in Saudi Arabia.
Your system and its nightly backups are on servers in Saudi Arabia. Outside that line there is only you: your team signing in, and your copy when you download it.
Saudi Arabia
Its database, your files and your settings, on servers in Saudi Arabia, running here day and night.
A full copy every night between 2 and 5 am. Run along the nights to see when each one is deleted.
Signing in from a browser, anywhere
Downloaded to your computer, whenever you like
Through a one-time linkYou grant access, and you take it back. Even our support team reaches your system only with a pass you grant — and it expires on its own.
Your team here is an example: you create their accounts, decide what each can reach, and take it back whenever you choose.
Not granted. Our team has no way into your system.
Grant it from your dashboard when you need us: we sign in under our own name, every change is recorded in your system's history, and it expires on its own after 24 hours.
A working model of the same pass in your dashboard.
Nightly backups, updates and health checks run on the server by themselves; none of them needs anyone to sign in to your system.
We restore your access to your system when you ask, and our log records who did it and why.
No one on our team reaches the admin console without two-step verification. It is a requirement, not an option.
None of it needs setting up. It is how every system we run works, from its first day.
Certificate valid, renews automatically
Every connection to your system is over HTTPS, so what passes between your team and your system can't be read on the way. The certificate renews itself before it expires.
Every customer has a separate system with its own database, its own database user and its own folder of files. Your records never share a table with another business's.
288 checks a dayEach column is an hour
We ask every system whether it is answering, every 5 minutes, day and night. Two misses in a row and our team is alerted.
Two-step sign-in is there to turn on, passwords known from leaks are refused, and five wrong attempts pause sign-in for 15 minutes. A new browser, a new password or a new email: you hear about it.
The server opens to the internet for two things only: the encrypted web your team uses to reach your system, and our administration, by digital key. Everything else is shut.
We write to you directly as soon as we know — not once the story is tidy — again whenever something changes, and once more when it is closed. These are the messages as they would reach you. We hope you never receive them.
When it began and when we found out, without jargon.
Which data, over which period, and what wasn't touched.
Right now, step by step.
If anything is needed — a new password, say — we say so plainly.
If you think you've found a security problem in RAMCORE, tell us what you found and how to reproduce it. We will reply, keep you posted while we fix it, and thank you for it.
Write tohello@ramcore.saWhat we ask of you
We would rather keep you by being worth staying with than by making it hard to go. Leaving takes three steps.
From your dashboard: your database and your public and private files, through a one-time link that works for 15 minutes.
It's a standard ERPNext backup. It restores on any ERPNext of the same version — your own server, or another provider's.
Your system stops at the end of the paid period and its data is kept until you decide. Deleting it is your call alone, confirmed by typing its address.
Exit feeSAR 0
What you paid for the current period isn't refunded, and nothing more is charged.
You do. The business data in your system is yours. We work with it only to run, support and protect the service, or when you ask us to.
In Saudi Arabia, on Oracle Cloud. Your system and its nightly backups stay in the Kingdom, and each customer's system is isolated from the others.
Our support team signs in to your system only with a support access pass you grant from your dashboard. It expires by itself after 24 hours, you can revoke it sooner, and every change they make shows under their own name. The automatic work — nightly backups, updates, health checks — runs on the server without anyone signing in to your system.
No. Each customer's system is separate, with its own database, its own database user and its own files. Another business on our servers has no way into yours.
Everything between your team and your system travels encrypted over HTTPS, with a certificate that renews itself. The server itself is closed to the internet except for the web, and the database can't be reached from outside.
As the account owner, ask us and we restore your access to your system. Every reset is recorded in our log with who did it and why. You can also hand ownership of the account to someone else on your team from your dashboard.
Yes, at any time. Download a full backup — your database and your files — from your dashboard. It's a standard ERPNext backup, and there is no exit fee.
Your system stops at the end of the period you paid for, and its data is kept until you decide what to do with it. Download your backup before you delete the system.
Write to hello@ramcore.sa with what you found and how to reproduce it. We will reply and keep you posted while we fix it.
This page is about the business data inside your system. What we collect about you as our customer — your sign-in, your billing details — and how we use it is in our privacy notice. Read the privacy notice