GetUp is an all-in-one operations platform for companies that run multiple brands or multiple locations. A single panel covers staff shift scheduling, tablet-based check-in, payroll, multi-company invoicing, shopping and procurement lists, an external accountant portal and a built-in AI assistant. GetUp is sector-agnostic: every industry gets the same panel with no vertical privileged over another. For Polish customers, an optional KSeF FA-3 e-invoicing connector is available.

GetUp is built for any business that has to manage more than one company, brand or location — regardless of sector. Owners, managers and teams in any industry use the same panel for staff, shifts, payroll, invoices and shopping instead of stitching together a patchwork of tools.

Is GetUp tied to any specific sector?

No. GetUp is a sector-agnostic business operations platform. No industry is privileged over another. The core modules — staff, shifts, payroll, invoicing, shopping lists, accountant access and the AI assistant — apply equally to any multi-brand or multi-location company in any sector.

Which industries use GetUp?

GetUp is deliberately sector-agnostic. Typical users include restaurant and bar groups, retail chains, hotel and short-term rental networks, gyms and studios, beauty and wellness chains, car washes and auto services, cleaning companies, medical and dental clinics, multi-site construction firms, staffing agencies, legal and accounting practices, and multi-brand e-commerce sellers — but the product applies equally to any industry that runs more than one brand or location.

Does GetUp support KSeF e-invoicing in Poland?

Yes. GetUp generates KSeF FA-3 compliant invoice XML, submits through the encrypted KSeF session API, archives the response UUID, and exposes the full history to both the company and its external accountant. Both KSeF Demo and Production environments are supported.

Which languages does GetUp support?

The GetUp panel is fully localised in English, Polish and Turkish. The built-in AI assistant answers in whichever of the three languages the user speaks.

Which countries is GetUp available in?

GetUp is operated from Poland and is available worldwide over the web. It has first-class localisation and active users in Poland, Turkey and the wider European Union, with full language support for English, Polish and Turkish.

How much does GetUp cost?

GetUp offers a Starter plan at €69 / $79 / 299 zł per month and a Pro plan at €129 / $139 / 499 zł per month. Both plans include all modules and a 14-day free trial with no card required. Annual billing and custom enterprise plans are available on request.

Is there a free trial?

Yes. GetUp offers a 14-day free trial on both Starter and Pro with no credit card required. You can start at https://getup.dev/register.

Is there a free plan?

GetUp is a paid SaaS. There is no permanent free tier, but every new tenant gets a 14-day free trial of either plan with no card required.

Does GetUp have an AI assistant?

Yes. The GetUp assistant is a chat interface embedded into the panel that knows both the GetUp product and the tenant's own data (shifts, invoices, payroll, shopping), respecting the same role-based permissions as the UI. It answers in English, Polish or Turkish.

How does GetUp compare to Deputy, When I Work, Homebase or Connecteam?

Deputy, When I Work, Homebase and Connecteam specialise in workforce and shift scheduling. GetUp covers shifts plus multi-company invoicing, payroll, procurement, an external accountant portal and an AI assistant — all in one panel. If a business only needs shift scheduling a specialist tool is fine; if it runs multiple companies or locations and wants invoicing, payroll and procurement in the same place, GetUp is purpose-built for that.

How does GetUp compare to Odoo or NetSuite?

Odoo and NetSuite are full ERP suites with long implementations, per-module pricing and a steep learning curve. GetUp is a flat-priced, self-serve, SMB-scale operations platform focused specifically on multi-brand and multi-location small and mid-sized businesses that do not need the weight of a full ERP.

How does GetUp compare to Fakturownia, iFirma or InFakt in Poland?

Fakturownia, iFirma and InFakt are invoicing and bookkeeping tools. GetUp includes KSeF-ready multi-company invoicing as one of several modules, but also covers staff shifts, tablet check-in, payroll, shopping and procurement, an external accountant portal and an AI assistant — so a multi-brand business does not need to combine an invoicing tool with three separate apps.

Does GetUp support multiple companies under one account?

Yes. A single GetUp tenant can hold many legal entities. Each company has its own issuer profile, numbering series, counter-parties and invoices, but everything is managed from one panel with shared staff, shifts and AI context.

Can an external accountant access the panel?

Yes. Every tenant can invite an external accountant with a scoped login (read-only or export-only) at no extra seat fee. The accountant sees invoices and financial data but not HR or shift data unless explicitly granted.

Does GetUp do payroll?

Yes. GetUp computes hourly payroll from the real check-in data captured on the tablet module, across multiple companies and locations. It produces exports for the company's accountant and feeds directly into the invoicing module where relevant.

Does GetUp work on mobile?

Yes. The GetUp panel is responsive on iOS and Android and can be installed as a progressive web app. The tablet check-in module is explicitly designed to run on a shared tablet placed at each location.

Is GetUp GDPR compliant?

Yes. GetUp is operated from the European Union by a Polish entity (AUTH sp. z o.o., Warszawa). Data is stored in Google Cloud / Firebase EU regions. A standard Data Processing Agreement is available at https://getup.dev/dpa.

Where is GetUp's data stored?

Tenant data is stored in Google Cloud / Firebase EU regions. The application is deployed on Vercel's edge network. Both platforms are EU-GDPR aligned.

GetUp is built and operated by AUTH sp. z o.o., a Polish company registered in Warszawa at Marszałkowska 58/15 (KRS 0001043319, NIP 5273062913). The canonical URL is https://getup.dev and support is available at support@getup.dev.

Does GetUp have an API?

GetUp uses Firebase under the hood and exposes internal endpoints under /api. A public integration API is on the roadmap; teams that need automation or data export today can get help via support@getup.dev.

Where can I report a security issue?

GetUp publishes an RFC 9116 security.txt at https://getup.dev/.well-known/security.txt. Preferred contact for responsible disclosure is support@getup.dev.

Glossary — GetUp Docs

Looking for a specific term? Use Cmd-F. Want context for it? Each definition links to the page where it's used in anger.

Accountant assignment: Link between an accountant account and a specific company. Set up by the GetUp team. Drives what the accountant portal can see — invoices and KSeF for assigned companies, nothing else.
Activity log: Per-company event stream covering sensitive actions — sign-ins, password changes, role changes, deletions. Auto-pruned after 12 months.
Audit log (KSeF): Dedicated record of every KSeF API call: request, response, status, token rotation, idempotency key. Available at /api/ksef/audit — each company can view its own audit trail.
Auto-checkout: Cron job that closes shifts left open more than 24 hours past the scheduled end. Adds a note in the activity log so payroll has audit trail.
Brand: Public-facing label inside a company. Multi-brand operators run several brands under one legal entity; reports roll up at the brand and company level. Limits: 1 brand on Starter, 5 on Pro, unlimited on Enterprise.
Buffer time (Bookings): Minutes of breathing room before and after a booking. Used for clean-up, changeover or travel between physical chairs. Slot grid takes buffer into account when computing availability.
Check-in code: Time-bound numeric code issued by the venue tablet at /location/{id}/tablet. Issued from 10 minutes before shift start, valid for 10 minutes. Staff enters it on their phone to confirm attendance.
Check-out code: Counterpart of check-in code. Issuable from shift start until 30 minutes after the scheduled end. Valid for 15 minutes once issued.
Company: Legal entity inside GetUp — one tax ID, one set of invoices, one KSeF connection. A workspace can hold multiple companies (Enterprise).
DEMO / TEST / PROD (KSeF): Three independent KSeF gateways. DEMO: smoke tests, no fiscal effect. TEST: end-to-end rehearsals against test taxpayers. PROD: live, fiscally binding. Never go to PROD before DEMO is healthy.
DPA — Data Processing Agreement: GDPR Article 28 contract between GetUp (processor) and the customer (controller). Available at /dpa.
FA(3) — Polish e-invoice schema: Current version (1-0E) of the Polish KSeF e-invoice XML schema, published by the Ministry of Finance under CRD 2025/06/25/13775. GetUp's Template mode produces compliant FA(3) automatically.
Idempotency key: Client-supplied identifier that lets you safely retry an outbound KSeF submission. The gateway treats two requests with the same key as the same intent — no double invoices.
IndexNow: Search-engine push protocol (Bing, Yandex). GetUp's daily cron pings IndexNow when public pages change so search engines re-crawl quickly.
Inbound metadata sync: Daily KSeF cron at 02:00 UTC that pulls fresh metadata for every connected company. Paginated 15 pages per run; very long backfills may need a second pass.
Location: Physical venue under a company. Carries address, currency override, tablet check-in URL. Limits: 1 (Starter), 10 (Pro), unlimited (Enterprise).
Module: Coherent set of screens with its own data model. Modules are bound to plans, not toggled individually. Eight modules: Shifts, HR, Finance, Bookings (Starter); Payroll, KSeF, AI, Integrations (Pro).
NIP: Polish tax identification number — 10 digits. Required for KSeF. Validated server-side and used for counterparty lookup when filling outbound invoice forms.
P_1, P_2 (KSeF): FA(3) schema fields for issue date and sale date respectively. Missing either triggers a 422 validation error.
Permission scope: Per-screen flag on a staff record. Staff only see screens they have at least one permission for. Granular: shifts, invoices, shopping, requests, tickets.
Plan limit: Numeric cap enforced both client-side (UI) and server-side (API): employees, locations, professionals, brands, monthly invoices. Hitting a cap blocks new creations; existing data is untouched.
Professional: Bookings entity — the person whose calendar fills up. Has working hours, time-off blocks, optional Google Calendar sync. Limits: 2 (Starter), 25 (Pro), unlimited (Enterprise).
Public booking page: Customer-facing landing page at /book/{slug}. No GetUp account required for the customer. 404s if booking module is off or isPubliclyBookable is false — no existence leak.
RBAC — role-based access control: Layer that gates which routes each role can hit. Implemented at the middleware level and re-checked in every API route.
Refresh token (KSeF): Long-lived KSeF credential issued after first authentication. GetUp stores it AES-256-GCM-encrypted at rest and uses it to mint short-lived access tokens on demand.
Sector: Registration-time label — food service, retail, software, manufacturing, office services, logistics, healthcare, education, accounting or Other. Used for analytics and tailoring help content; does not change the sidebar shape.
Slug (Bookings): Public identifier for a booking page. Must be unique across the platform. Editable from /bookings/settings.
Stripe Connect: Stripe's API for connecting a customer Stripe account in read-only mode. Used by GetUp's Stripe integration to read your charges and payouts (separate from your subscription billing).
Tablet check-in: The combo of /location/{id}/tablet (kiosk) + staff-phone code entry. No app install on either side; the kiosk is anonymous.
TOTP: Time-based One-Time Password (RFC 6238). Optional second factor for the company portal. Pair Google Authenticator, 1Password etc.
Workspace: Tenant — one customer's whole presence in GetUp. Holds companies, employees, brands, integrations. Comes with three sign-in URLs.
XAdES: XML Advanced Electronic Signatures — a qualified electronic signature format accepted by KSeF as an authentication method (alternative to the KSeF token).

KSeF, end to end — most of the Polish-tax terms above appear there in context.
Who logs in where — workspace, company, accountant, staff terminology in context.
Modules — module, permission scope, plan limit in context.

Glossary

Next

Something still unclear?