This comparison is unlike the others: Pontomais is not in Nimbos's place. It records the working day; Nimbos records work per project — and the sum that matters is the difference between the two.
From R$9.00 per licence/month, minimum R$90.00 · parameters set per company, proposal and project
Their page is about the working day, and it is strong there: simple punching, offline punching, a shared device with QR code and facial recognition, punching by WhatsApp, an exceptions report that flags odd punches and missing ones before the close, an electronically signed timesheet mirror without an A1/A3 certificate, and direct export to payroll. They state compliance with Brazil's Portaria 671 and with the LGPD. Anyone already using it should not switch because of Nimbos — Nimbos is not a time clock, and the comparison below exists to show where one ends and the other begins.
| Capability | Pontomais | Nimbos |
|---|---|---|
| Overtime | The page lists an overtime forecast under real-time management, alongside hour bank, attendance and lateness. The ruler is the working day's, and the destination is payroll. | Nimbos calculates overtime by your company's labor agreement rules: bands, weekend and holiday premiums and the night premium, all configurable — the defaults of a real agreement come ready to adjust. |
| Hour bank | An hour bank appears under real-time management. It is the WORKING DAY's bank — exactly the data Nimbos consumes from the clock, not something it reinvents. | Nimbos keeps the hour bank under the collective labor agreement: configurable cycle, factors for working and non-working days, night premium and balance caps — the balance turns into time off and rolls into the next cycle. |
| Time clock | It is their whole product, and the best in this table on this point: simple punching, offline, shared device with QR code and facial recognition, punching by WhatsApp, and the electronically signed mirror. | Nimbos checks, day by day, whether clock-ins and logged hours match: who clocked in without logging hours, who logged hours without clocking in, and where the sources diverge — without demanding hours on holidays, during vacation, or for the day that hasn't closed yet. |
| Margin per contract | The page covers neither cost per hour nor margin per contract — the product is about the working day and HR, not about projects. | Nimbos shows each contract's margin throughout the month — hourly cost and price per role, negotiated contract by contract. On invoicing, it stamps the price and cost used: renegotiating later does not touch an already invoiced month. Cost is visible only to those with permission to see it. |
| Month-end close | The close their page describes is the ATTENDANCE close: an exceptions report before closing, and direct export to payroll systems. | Nimbos requires approval per project before closing: any recorded approval locks the month for editing. Once closed, the month freezes the quantity and the clause in force — renegotiating later does not move a closed month. First you define how much of the hours becomes billing, then you close, only then you invoice — and it is on invoicing that the price and cost get stamped. |
| Invoicing | The page does not list issuing an invoice to the client. | Nimbos calculates the invoice amount and line items from the closed month. In Barueri-SP, it also builds the submission file in the city hall's layout — sending it remains a separate step. |
| Bringing the history | The page cites integrations with payroll and HR record systems (Apdata, RH Digital) and with Feedz. Bringing across a history of project time is not its subject. | Nimbos connects through the API and brings the history over month by month, creating any missing projects and people. Syncing the same month again does not create copies — Nimbos mirrors the source, and hours already invoiced, approved, or in billing review are preserved and reported. |
| Where the data lives | The page states alignment with LGPD guidelines and 99.8% uptime. Which region the data sits in, it does not say. | Nimbos hosts the data in Brazil, each company isolated from the others in the database, and each person sees only what concerns them. |
| Price | Not published. The page asks you to request a quote, picking a headcount range. | From R$9.00 per licence/month, with a R$90.00 minimum invoice; without commitment, R$20.00 per licence/month, cancel anytime. Every module is included in the price. |
Pontomais by VR does not publish pricing: the page asks for a quote, choosing a headcount range (pontomais.com.br, September 2026). Nimbos starts at R$9.00 per license/month, with a minimum invoice of R$90.00, and the figure is published.
The price is per seat, not per login: it counts every person whose hours exist in Nimbos, including those who never sign in. If someone imports the hours of ten others, that is eleven seats — the importer's and the ten imported.
There is no figure on the other side because the vendor publishes none. What is described here is what their page says about the product, read in September 2026.
This is not about migrating, it is about RECONCILING. Nimbos reads what the clock recorded and checks it, day by day, against what was logged per project: who punched and did not log, who logged without punching, and where the two sources diverge — without counting holidays, leave, or the day that has not closed yet.
The market matrix compares six tools in one table, with the official source for each of them.
Message us on WhatsApp. If you already have a time-clock system, tell us which — the conversation is about reconciling, not replacing.
Sales channel. If your company already uses Nimbos, support goes through your administrator.