ADM · on-premise

The suite is the same. The hardware conversation is separate.

For the person who has to sign the security review. We will not invent a certification we do not hold. We will tell you where data sleeps, how a tenant is cut, and that we stay for deploys.

  1. TEN
    A tenant is a company domain Cloud: acme.ubirimi.net. On-premise: the hostname you choose. People, projects, and permissions do not leak across tenants.
  2. HW
    Your hardware, or ours Cloud is a monthly band. On-premise is capacity, identity, and where the database and object storage live. We plan, build, and operate with you — including the 2 a.m. surprise.
  3. S3
    Issue attachments are object storage Yongo attachments are not a disk folder under the web root. They require S3-compatible storage (MinIO locally; the bucket you name in production). Documentador assets follow the same idea.
  4. ID
    Identity is yours to discuss Administrators create the tenant and the first users. How that joins your directory is part of the on-premise conversation — we do not print “SSO included” as a slogan and then discover your IdP on week six.
  5. PRM
    Permissions are schemes, not a global admin checkbox Yongo permission schemes, issue security, Documentador page restrictions, Help Desk portal vs agent. The application looks up the scheme. It does not assume everyone is a developer.
  6. TRIAL
    Fifteen days, no card on the form Cloud trial creates a tenant. We do not collect a PAN to start. On-premise is quoted, not a credit-card flow.

What we will not claim

No badge row.

If a questionnaire needs SOC 2, ISO, or a pentest PDF, ask. We will send what we have and say what we do not. Invented shields on a marketing page are how reviews die.

  • +Same suite on cloud and on-site — not a forked “lite”
  • +Object storage for issue files
  • +Tenant isolation by client
  • +People who still answer after go-live

FAQ

Questions people actually ask

Is on-premise a different, lighter product?
No. The suite is the same. Hardware you control is a conversation about capacity, identity, and where the database and object storage live.
Where do issue attachments live?
S3-compatible object storage — MinIO locally, the bucket you name in production. Not a folder under the web root.
Do you publish SOC 2 or ISO badges?
Not as invented shields on a marketing page. If a questionnaire needs a report, ask — we send what we have and say what we do not.