Already a client? Open a ticket in the support portal. New here? Email us — a real person reads every message.
Sign in to the support portal with your existing credentials to open and track tickets. Email updates flow both ways automatically.
Tell us about your client book, which payroll vendors your clients use, and what you're trying to solve. We'll take it from there.
For a supported payroll vendor, a new client is usually live within a week of receiving credentials and a column-map review. Adding a brand-new payroll vendor takes longer — typically a few days of development plus a test cycle.
We support several payroll vendors today and add new ones on request. Because the platform is built around a vendor-agnostic extractor interface, a new vendor is usually only a few days of work. Reach out with what your clients use.
No PHI in our application database. SSNs are masked to last 4 in operational data; full identifiers only land in encrypted attachments in AWS S3 (KMS) and only behind explicit access gates. Operational data is encrypted at rest. See the security page for more.
Sync failures land in a per-client manual-action queue inside the admin portal with the category, severity, and the employee context your operator needs to fix it. Critical failures also trigger an operator email. We monitor every run on our end.
Every record in the database is scoped by client. Row-level security policies enforce isolation at the database layer, not just in the application. Storage keys carry the client ID. Logs and audits are per-client. Cross-tenant access is structurally impossible, not just discouraged.
Yes — the platform is built around a white-label posture. Your brand can appear on the portal, the emails, and the invoices your end-clients see.