Replace your company’s stack. One module at a time.

ViniOffice is the operating platform for your workplace — one connected system for the people, finances, assets and day-to-day operations a company runs on, instead of a pile of disconnected tools. Three modules are live today: employee records and org structure, leave and time-off with a full balance ledger, and attendance with shifts and rosters. The rest of the platform — payroll, expenses, performance, recruiting, assets, documents and more — is on the roadmap and lands on the same directory and permission model.

That is the right question to ask, and the answer is in the order we build in. The employee directory, the permission model, the approval engine and the audit trail are already built and running in production — and payroll, expenses and assets don't rebuild any of them, they read from them. The nth module is far cheaper than the first, which is why the sequence matters more than the module count: each one is deliberately the cheapest useful thing we can build on what already works. Look at the build order and the ship log on our homepage and judge us on what has actually landed, and how fast, rather than on a roadmap.

Honestly: they are mature products and we are not. If your team is already happy on an established HRMS, we're not the switch — we're built for teams still running on spreadsheets, shared drives and email approvals. What we offer instead of maturity is one genuinely shared foundation: every module reads the same directory, the same permission model and the same approval engine, rather than modules that were separate products first and had to learn to talk to each other. Concretely, that means a leave ledger where every balance reconciles line by line months later, and tenant isolation and an append-only audit trail that the database enforces rather than application code.

ViniOffice is built for small and mid-sized companies that want to run their company from one connected platform instead of a stack of separate tools. It serves HR teams, managers, employees, and IT/security stakeholders, and expands to finance, workplace and operations as those areas of the platform ship.

ViniOffice isolates each organization's data at the database level using PostgreSQL row-level security, in addition to application-layer checks — the app connects as a role that cannot bypass those policies, so a bug in application code still can't read another tenant's rows. On top of that: role-based access control with per-role reach, AES-256 encryption of national IDs and bank details, and an audit trail that records every change — who, what, when and from where — and is append-only at the database itself, so no code path can rewrite history. Changes to people records, pay and leave policy are logged field by field, with sensitive values like salary masked in the log so the audit trail never becomes a second copy of the data it is auditing. SAML single sign-on and SCIM provisioning are on the roadmap, not available yet.

Not yet. SAML single sign-on and SCIM 2.0 provisioning are on the roadmap and are not available today. Sign-in is email and password with token-based sessions; you can bulk-load people from CSV, and access is revoked immediately when someone is offboarded. If SSO is a requirement for your rollout, tell us on the early-access form — it helps us sequence it.

Yes — ViniOffice is modular, and your workspace only shows the modules you're using. During early access we switch modules on for your organization rather than exposing a self-serve marketplace, so tell us what you need. Each live module brings its own settings and approval configuration.

Partly, today. You can create an employee (individually or by CSV import), capture their profile, job assignment and emergency details, and move them through guided lifecycle stages — pre-onboarding, onboarding, active — with HR activating them in one step. The full self-service new-hire wizard, with policy acknowledgements and role-targeted checklists, is on the roadmap.

Not yet. An "Ask HR" assistant — answering policy and leave-balance questions from your own data — is on the roadmap. We're building the connected record it would need to answer from first; an assistant on top of half the data would just be a chatbot that guesses.

ViniOffice is in early access, and we're running a pilot with a small first group of companies. The people side of the platform — employee records, leave and attendance — is live and in real use today. Join the waitlist on the site to get access and help shape what ships next.

Your data stays yours, and you can have all of it as CSV whenever you ask — the employee directory and profiles, the full leave ledger with every accrual and adjustment, and your attendance records. Today you ask us and we send it; self-serve export from inside the app is on the roadmap. That holds whether we shut down or you simply decide to leave: you go with everything, in a format any other system can read. We'd rather you stay because the product is good than because your data is stuck in it.

We haven't set pricing yet — the product is still being built and the pilot is free, with no card and no invoice. What we can commit to now is how the change will happen: pilot companies get plenty of notice, nothing converts to a paid plan automatically, and you decide for yourself whether to continue.

Nothing while we're in pilot. Companies in the pilot programme use ViniOffice free, with no card and no invoice — we're still building, and we'd rather have your feedback than your money. We haven't set pricing yet; when we do, pilot companies get plenty of notice and decide for themselves whether to continue. There's no automatic conversion to a paid plan.