Your account
Sign-in is protected, and privileged actions on our side require a second factor. We never ask for your password, and nobody at Metranti can read it.
Security
Your work deserves professional safeguards.
You are trusting us with how your business runs. These are the protections that come as standard — not as an upgrade, and not as something you have to configure.
Standard, not optional
Every protection listed here applies to every customer, on every plan, from the first day.
Your organisation is separate
Your projects, documents and conversations belong to your organisation and are not visible to any other customer. Separation is enforced by the system itself, not by a convention people have to remember.
Who can see what
People in your organisation get the access their role needs. Someone who can read a proposal is not automatically someone who can approve one.
Your files
Documents are stored privately and never on a public address. Every download is authorised first, links are short-lived, and files are checked for integrity so what you download is what you uploaded.
A record you can rely on
Approvals, proposals and delivery decisions stay part of your project history. Contracts and invoices cannot be quietly altered or removed later.
Payments stay with the payment provider
Card details are never entered into or stored by Metranti. Payment happens on the provider’s own hosted page, and we only ever see the outcome.
Backup and recovery
Your data and documents are backed up together on a schedule, and restoring them is rehearsed rather than assumed. A backup nobody has tested is not a backup.
People decide the things that matter
Commercial and delivery decisions with real consequences are reviewed by a person. Nothing automatic issues a refund, changes a contract or ships to production on its own.
For the technical reader
- Tenant isolation is enforced at the database level as well as in the application, with separate database roles for customer and staff traffic.
- Every write requires an idempotency key, so a retried request cannot charge, deliver or record anything twice.
- Inbound provider callbacks are authenticated and deduplicated, and are recorded before they are acted on.
- Rate limiting is shared across instances, and the paths that protect credentials or money refuse rather than degrade when it is unavailable.
- Stored files use server-generated keys, are validated on type and content, and are served only as attachments.
- Backups cover the database and the file store together, and a restore is verified on a schedule.
Responsible disclosure
Found something?
If you believe you have found a security issue, tell us and we will look at it properly. You will get a reference and a person, not an auto-reply.