How to read this pageEach field explains what it is for, what to enter and an example. If your company does not use a feature, that field may not appear for your profile.
1. What Licensing is for
Licensing controls which capabilities each customer can use and how the environment is provisioned.
Customer→Plan→Deployment→License→Database / tenant→Company / admin
2. New customer: field by field
This screen is administrative and should be used only by authorized staff.
| Field | What it is / why it exists | What to enter | Example / rule |
|---|---|---|---|
| Code Required | Internal customer identifier in license control. | Use a unique, stable code. | May be defined by operations. |
| Legal name / group Required | Customer or economic group name. | Enter the official/recognizable name. | Used in the control plane. |
| CNPJ Optional | Brazilian corporate tax ID. | Enter when applicable. | Helps identification. |
| Plan Required | Contracted plan/license version. | Choose an available plan. | Controls capabilities. |
| Deployment Required | Infrastructure model. | Choose Cloud Managed, Enterprise Dedicated or On-Premises Enterprise according to contract. | Controls provisioning. |
| License mode Required | How the license is validated. | Choose Online/lease or signed Offline according to policy. | Depends on the environment. |
| Industry Optional | Code of the customer's initial industry experience. | Enter the contracted pack/industry code. | Example: AUTO_REPAIR. |
| First company name Required | Initial company created inside the tenant. | Use a name the customer recognizes. | Example: Main Workshop. |
| Initial administrator Required | Initial administrative login. | Enter the user that will receive first access. | Review security after onboarding. |
| Provision now When applicable | Starts database/tenant provisioning when applicable. | Enable only when deployment is ready for provisioning. | Use idempotency to prevent duplicates. |
3. Deployment models
Infrastructure changes according to customer size, governance and operational need.
| Model | When to use it |
|---|---|
| OIKVRA Cloud | Managed operation with fast deployment. |
| Dedicated VPS | Larger customer requiring dedicated resources/isolation. |
| On-premises / datacenter | Customer requiring execution on its own infrastructure while retaining centralized licensing. |
| OIKVRA Appliance | Dedicated standardized hardware for store, branch, edge or local operation. |
| OIKVRA OS | Standardization of dozens or hundreds of terminals, POS endpoints, kiosks and mini PCs. |
| Isolated BI | Read-only clone database isolated from the operational database. |
4. Customer DBA and BI
Customer technical access must preserve isolation and product integrity.
DBAWhen a customer requires DBA access, use a dedicated environment according to policy. Do not grant write access to the shared central database.
BIFor customer BI, prefer a read-only clone database with resource limits. Heavy analytical queries stay outside the main operational database.