The current list of products, features, limits, prices, billing cycles and commercial availability is presented in the public catalog at https://uqbitz.com/pricing, in the ordering dashboard or in a commercial proposal. Only services identified as available for purchase are part of the current offering; features marked as preview, beta, experimental or roadmap are not contractual obligations.
The order, commercial proposal and plan specifications displayed at the time of purchase supplement these Terms. In the event of a conflict, the specific instrument prevails as to scope, price, cycle, resources, term and service level.
2.1. Platform, Hosting and Applications
UQBITZ offers account plans for access to and management of the platform and isolated per-project hosting environments called “Shabti,” intended for websites, WordPress, PHP/OpenLiteSpeed applications, Bun/Node.js, Python, Ruby, Go, Rust and other compatible technologies made available in the catalog.
Each project is provisioned with the processing capacity, memory, storage, transfer, number of environments, domains and other limits corresponding to the contracted plan and Shabti size. Additional resources, such as storage, backups, snapshots, dedicated IP, licenses, managed support or extra capacity, may be purchased when available.
Free or trial plans may have an expiration period, reduced capacity, a platform subdomain and no included SLA or backup. At the end of the stated period, CLIENT must move to a paid plan or export its data before deactivation.
Infrastructure may use the providers listed on the Suppliers and Subprocessors page, according to the purpose, region and service architecture. UQBITZ may replace or combine providers without materially reducing the contracted scope.
The platform provides artificial intelligence features for operational support, diagnostics, automation and service, according to the plan and the current catalog. Their use may be charged by consumption, under the conditions displayed at the time of purchase. Running these features involves specialized processing providers, and the processing of any personal data contained in the requests follows the Privacy Policy.
Infrastructure updates and maintenance will be performed by UQBITZ and its partners. Scheduled maintenance and availability targets will follow section 3 and the terms of the contracted plan.
2.2. Managed Databases
UQBITZ offers managed PostgreSQL, MongoDB, MariaDB and ClickHouse instances according to the engines, sizes and regions available in the catalog.
The service may include provisioning, operational monitoring, credentials, networking, lifecycle operations, backups, restoration and export. Capacity, retention, backup frequency, availability, transfer limit and support depend on the contracted plan or proposal.
CLIENT remains responsible for data modeling, quality, lawfulness and content; application users and credentials; queries, indexes and workloads it runs; and maintaining its own exports consistent with its continuity needs. Restorations replace or recreate data according to the selected operation and may cause temporary unavailability.
Free trials, when offered, will have the duration, capacity and retention stated at the time of purchase and may be terminated at the end of the period if not converted to a paid plan.
2.3. Professional Email
UQBITZ offers two categories of professional email:
- UQBITZ Email Pro: mailboxes hosted and administered on the platform infrastructure, under plans with their own storage and limits;
- Google Workspace: licenses resold and administered by UQBITZ, in flexible or commitment models and the SKUs available in the catalog.
The scope may include activation, initial DNS configuration (MX, SPF, DKIM and DMARC), mailbox or license administration and billing intermediation. Message migration, device configuration, training, advanced recovery and extraordinary support may be billed as technical services.
For Google Workspace, availability, features, limits, security of the underlying service and commitment rules are defined by Google. Commitment licenses remain subject to the contracted term and quantities even when CLIENT stops using an account. Flexible models follow the cycle and conditions displayed at purchase.
CLIENT is responsible for message content, lawful use of the service, credential protection, storage management and compliance with applicable UQBITZ and provider policies.
2.4. Domain Registration and Management
UQBITZ offers international domain registration and management services through Enom. For national domains (.br), registration is carried out with Registro.br, with an administrative fee added to the official value.
Ownership
CLIENT is the sole and legitimate owner of the registered domain. UQBITZ acts exclusively as an intermediary in administrative and technical management, not having any rights over the domain.
CLIENT is responsible for the veracity and updating of the domain's registration data (WHOIS), exempting UQBITZ from any responsibility for incorrect or outdated information.
Renewal
Domain renewal is the exclusive responsibility of CLIENT.
CLIENT may choose automatic or manual renewal at the time of contracting or later, upon request.
UQBITZ will send expiration notifications 60 (sixty), 30 (thirty) and 15 (fifteen) days in advance to the registered email. Failure to receive notifications, for any reason, does not exempt CLIENT from responsibility for timely renewal.
It is strongly recommended that the renewal payment be made at least 7 (seven) days before the expiration date, avoiding the risk of losing the domain due to failed bank transactions, compensation delays or systemic unavailability.
Renewal is subject to full payment of the corresponding invoice before the domain's expiration date.
Expiration and loss of domain
Domains not renewed by their expiration date will be subject to the registrar's (Enom or Registro.br) expiration policies, which may include:
- Immediate suspension of the domain’s operation;
- Grace period for renewal, when available;
- Release of the domain for registration by third parties.
Important: Some registrars do not offer a grace period or redemption, and the domain may be permanently lost within up to 10 (ten) days after expiration. UQBITZ has no control over these policies and does not guarantee the possibility of recovery.
UQBITZ is not responsible for domains expired due to non-payment, nor for domains registered by third parties after release.
Where recovery is technically possible, registrar fees will be passed through in full to CLIENT, together with the amount corresponding to the time spent by UQBITZ under the current technical hours price list.
Transfer to another registrar
CLIENT may request the transfer of the domain to another registrar, provided that:
- The domain is active and not expired;
- There are no outstanding debts related to the domain;
- The domain is not in a lock period (60 days after registration or last transfer, according to ICANN rules);
- The request must be made at least 30 (thirty) days before the domain's expiration date.
Attention: Transfers requested with less than 30 days to due date may be refused or technically made impossible by the registrar. In these cases, you will need to renew the domain before transferring it.
Upon request, UQBITZ will provide the authorization code (EPP/Auth Code) necessary for the transfer. The deadline for providing the code varies from 5 (five) to 15 (fifteen) business days, depending on the registrar and domain extension.
The transfer of the domain to another registrar does not generate the right to a refund of amounts already paid.
Domain disputes
Any disputes related to ownership or use of the domain will be resolved directly between CLIENT and third parties, in accordance with the applicable dispute resolution policies (UDRP for international domains, SACI-Adm for .br domains).
UQBITZ will collaborate in providing information when requested by the competent authority or by CLIENT, for the purpose of defending its rights.
2.5. Technical Hours and Hours Plan
UQBITZ offers on-demand technical services measured in technical hours, purchased one-off or through the Hours Plan, as well as through a quotation or project proposal. Activities may include web development, design and UX, DevOps, consulting, bug and incident fixing, API integration, database migration, code review, contact forms, website maintenance and other services agreed between the parties.
Purchase models
- One-off hours: hours purchased for a specific request, without automatic renewal and without minimum commitment, according to the approved quotation;
- Hours Plan: a monthly number of contracted hours, with a Starter, Growth, Enterprise or equivalent current tier defined by the number of hours, the corresponding hourly rate and the conditions of this section;
- Fixed-price service or project: an amount defined in advance for a specified scope, assumptions and deliverables.
Billing and price list
Services are billed according to the time actually logged, the hours contracted in the Hours Plan or the approved fixed price. The current catalog may apply different hourly rates depending on volume, specialty, priority, time or nature of the request. Conditions negotiated and recorded in a proposal, order or contract prevail for that purchase.
Time is logged in exact minutes, without rounding. CLIENT may follow consumption through the dashboard, a report or another record made available by UQBITZ.
Hours Plan
- Purchase and summary of conditions: when purchasing, CLIENT chooses the monthly hours and accepts a summary of conditions — hours, tier, hourly rate, monthly minimum, minimum term with its end date, cancellation notice, withdrawal period, logging fraction and response times. The summary is recorded in the contract, sent by email and constitutes the express statement of the minimum term. The minimum term is accepted in a separate confirmation, apart from the acceptance of these Terms;
- Monthly minimum and unused hours: the contracted hours form the monthly minimum, billed even when usage is lower. The minimum reserves the team's capacity for CLIENT's plan; for that reason, hours not used in the month do not roll over, are not transferred and are not refunded. Hours above the contracted ones are billed at the same hourly rate;
- Billing: the plan is billed at the close of each calendar month. The first month is prorated to the days remaining from the purchase;
- Benefit and minimum term: the plan's hourly rate is lower than the one-off hourly rate, and the summary of conditions shows both. In return, the plan has a minimum term equal to the partial month of the purchase plus 3 (three) full months. Those who prefer no minimum term may purchase one-off hours by quotation;
- Changing hours: an increase applies to the whole current month and does not restart the minimum term. A reduction is only possible after the minimum term and applies from the month following the request;
- Cancellation: CLIENT may cancel at any time, with 30 (thirty) days notice. The plan ends on the last day of the month in which the notice completes; until then, the service continues to be provided and billed as usual, and the scheduled cancellation may be undone. Once the minimum term has been served, cancellation carries no penalty. Requested before the end of the minimum term, cancellation takes effect on that same date and subjects CLIENT to the penalty in item 10 — the plan is not kept alive by force until the end of the minimum term;
- Withdrawal: when purchasing through the dashboard, CLIENT may withdraw within 7 (seven) calendar days, without minimum term and without the monthly minimum. Hours performed at CLIENT's express request within that period are billed;
- Non-payment: under the standard schedule, if a plan invoice remains past due for 30 (thirty) days, the plan is suspended — no new requests and no work performed — and the monthly minimum stops being billed for as long as the suspension lasts, because a suspended plan is not reserving the team's capacity. Past-due amounts, charges and hours actually recorded before the suspension remain payable. Once the amounts are paid, the service resumes and the billing period in progress is extended by the time it remained suspended;
- Termination for non-payment: at 90 (ninety) days past due, the plan is terminated, without billing future months. If the minimum term is still running, termination subjects CLIENT to the penalty in item 10, in place of billing the monthly minimum until the end of the term;
- Penalty for breaking the minimum term: the minimum term exists as consideration for the hourly rate being lower than the ad-hoc rate — it is a discount granted up front in exchange for staying. If the plan ends before the end of the minimum term, whether by CLIENT's cancellation or for non-payment, a penalty equal to the discount already enjoyed is due: the difference between the ad-hoc hourly rate and the plan hourly rate, both stated in the summary of conditions at purchase, multiplied by the hours actually recorded and billed under the plan up to termination. The penalty is capped at the sum of the monthly minimums that would remain until the end of the minimum term, and may never exceed it; it does not apply to contracted hours that went unused. No penalty is due in the case of item 7 (withdrawal), on termination for UQBITZ's breach, on termination arising from a price adjustment or change of terms with which CLIENT does not agree, in acts of God or force majeure, or on any termination after the minimum term.
Requesting services
Requests must be sent through the official communication channels (dashboard, support system or email). In the Hours Plan, each request is recorded with the urgency stated by CLIENT and receives a first response within business hours (Monday to Friday, 9 a.m. to 6 p.m. Brasília time, except national holidays): critical urgency within 4 (four) business hours, high within 1 (one) business day and normal within 3 (three) business days. UQBITZ will assess each request and, when necessary, provide a time estimate before execution; an estimate that takes the month beyond the contracted hours depends on CLIENT's approval.
Services requiring the purchase of third-party resources (plugins, licenses, APIs, etc.) will have their costs disclosed to CLIENT in advance for approval.
General conditions
- One-off hours have no minimum commitment unless expressly stated in the quotation;
- Material changes to Hours Plan tiers or conditions will be communicated under the Official Communications section;
- Third-party resources, licenses, plugins, APIs, travel and expenses are not included in the hourly rate unless expressly stated.
Order of priority
Critical security issues or production outages may take priority over ordinary requests. Other requests will be handled according to urgency, the response times above, team availability and order of arrival.
2.6. Development, Projects and Migrations
UQBITZ develops and maintains websites, online stores, web applications, landing pages, integrations and custom digital solutions. It may also perform assisted migrations of hosting, WordPress, cPanel, email, databases and applications, subject to technical review and an approved proposal.
Engagement models
Services may be purchased at a fixed price, through technical hours (one-off or Hours Plan) or under another model expressly provided for in the proposal. Scope, deliverables, assumptions, schedule, environments, acceptance criteria, ownership of materials and payment terms will be defined in the specific instrument.
Unless otherwise stated, fixed-price work may require a down payment to begin and the balance at the agreed milestones. Scope changes, undisclosed dependencies, licenses and third-party services require new approval.
Execution and CLIENT collaboration
CLIENT must provide the materials, access, credentials, decisions and approvals needed for the work. Delays caused by these dependencies may change the schedule. UQBITZ may use development or staging environments before publication when appropriate.
CLIENT will have 10 (ten) business days to validate each delivery or stage unless the proposal provides a different period. A lack of response may be treated as acceptance of the stage after a validation request is sent through an official channel.
Migrations
Before a migration, UQBITZ may require access to the source environment, an inventory, a maintenance window, destination capacity and a valid backup. Compatibility and timing depend on the data volume, source-provider limitations, credentials supplied and platform differences.
UQBITZ does not guarantee complete migration of proprietary settings, licenses, unrecoverable passwords, corrupted data or incompatible components. The source environment must not be canceled until CLIENT has validated and accepted the destination.
Inactivity and project abandonment
If CLIENT fails to respond to requests necessary for the project, UQBITZ will make up to 3 (three) contact attempts through official channels. If no response is received for 90 (ninety) calendar days after the last attempt, the project may be closed in its current state, with billing for work performed and no refund for completed stages.
Content, materials and acceptance
CLIENT warrants that it has the necessary rights to all text, images, trademarks, data and other materials it provides, and remains responsible for published content and the lawfulness of its business. Delivery and publication may be subject to approval and payment of all amounts due.
Additional requests, corrections after acceptance or issues caused by changes made by CLIENT or third parties may be handled under a new quotation or technical hours.
2.7. Intellectual Property in Development Projects
This section applies to website, online store, web app, newsletter, landing page and other development projects contracted under a fixed-price quotation or technical hours.
Ownership and transfer
Delivery of the project to CLIENT will only occur after full payment of all amounts due.
Until full payment, all rights to the code, layout, design and other materials produced remain with UQBITZ.
Upon full payment, CLIENT receives:
- Perpetual, non-exclusive and non-transferable license to use the developed project;
- Full administrative access to the website or application;
- Files and deliveries according to the project modality (detailed below);
- Original design files, when produced by a designer hired by UQBITZ.
Delivery modalities depending on project type
WordPress with visual builders (Elementor and similar): The project is delivered published in the production environment. The models, templates and configurations are stored on the website itself, and there is no separate source code for delivery.
WordPress with custom theme: The source code is maintained in UQBITZ's private repository (GitHub). Upon request, CLIENT will receive full project ZIP file and/or theme ZIP file for installation.
Specific projects (web apps, systems, customized stores): The source code is maintained in a private UQBITZ repository (GitHub). Delivery can be carried out in the following ways, according to CLIENT's technical profile:
- Source code ZIP file;
- Granting access to the GitHub repository; or
- Transfer of the administration of the GitHub repository to CLIENT.
What delivering the repository transfers. The ZIP file, the granting of access to the repository and the transfer of its administration deliver custody of the code: from then on, CLIENT holds the files and administers the repository in the exercise of the license in the “Ownership and transfer” subsection. None of these delivery forms amounts to an assignment of copyright in the code — an assignment requires a specific written instrument under article 49 of Law No. 9,610/1998 and is not included in these Terms. Transferring the administration of the repository neither widens nor narrows the license granted, and UQBITZ ceases to administer it from the transfer onward.
Intellectual property of the code
The source code, algorithms, technical solutions, components and libraries developed by UQBITZ remain the exclusive property of UQBITZ, regardless of the project in which they were used. Custody of that code may be transferred to CLIENT according to the delivery form, without the transfer amounting to an assignment of the rights covered by this subsection.
CLIENT receives a usage license as described above, but does not acquire ownership of the code itself, and UQBITZ may reuse solutions, techniques and components in other projects.
The design, idea and specific business rules of the project belong to CLIENT.
Third-party software and resources
The following are not owned by UQBITZ or transferred to CLIENT:
- Third-party software used in the project (WordPress, WooCommerce, plugins, libraries), which remain subject to their respective licenses;
- Licensed stock images, fonts, and assets licensed under the terms of the original provider.
Retention due to default
In the event of default directly related to the project or contracted milestone, UQBITZ reserves the right to:
- Suspend access to project environments that remain under UQBITZ's management;
- Withhold the still-pending delivery of files, source code and access credentials;
- Postpone publication or migration of the project to a production environment until the default is cured.
File storage
UQBITZ will maintain project files for a minimum period of 12 (twelve) months after final delivery.
For CLIENTS with active services, such as hosting, maintenance or the Hours Plan, files will be retained for the duration of the contractual relationship.
After the above deadlines, there is no guarantee of availability of the original files.
Credits and portfolio
CLIENT authorizes UQBITZ to:
- Include discreet credit in the website footer (“coded by UQBITZ” or similar), with a link to the UQBITZ website;
- Use the project for portfolio purposes, institutional dissemination and demonstration of technical capacity.
If CLIENT does not wish the inclusion of credits or disclosure in the portfolio, it must expressly express its opinion at the time of contracting or during the development of the project.
Exclusivity clause
UQBITZ is not prevented from developing projects for companies in the same segment as CLIENT, except through a specific exclusivity agreement signed separately, with its own conditions and validity.
Post-delivery responsibility
After delivery and acceptance of the project, CLIENT becomes responsible for:
- Content published on the website;
- Updates and modifications carried out by yourself or third parties;
- Maintenance and updating of third-party software (WordPress, plugins, etc.);
- Security of access credentials.
UQBITZ is not responsible for problems arising from:
- Installation of plugins, themes or extensions not carried out by UQBITZ;
- Changes to the source code made without the participation of UQBITZ;
- Lack of software updates;
- Hacks or compromises resulting from weak or shared passwords.
Corrections required because of the situations above will be quoted separately under the current technical hours price list.
Termination during the project
In the event of contractual termination during the execution of the project, the provisions of the Contract Termination clause apply: the work actually carried out will be invoiced, and the delivery of partial work is conditioned on full payment of the amounts due.