Warp

Named systems cover every category the platform touches: accounting with QuickBooks Online and Xero on every tier, and NetSuite and custom ERP integrations at Enterprise; identity with Okta and Google Workspace, both sold as provisioning add ons at $5 per person per month; Slack, including Slack and email invoice submission for expenses; applicant tracking from Pro up; background checks through Checkr; 401(k) and benefits carriers, with enrollment and carrier sync run in house; and device management through Warp's own MDM agent.

The heaviest write is to a government counterparty. The agents open state tax accounts, submit registrations, hold the resulting agency credentials and file returns on schedule across all fifty states: whatever the transport, a write into an external system of record with legal effect. Provisioning creates real accounts too.

The published onboarding example creates a Google Workspace mailbox, a Slack account and a GitHub account and installs an MDM agent from one event, and offboarding revokes them. Employee data syncs both ways, so promotions, transfers and pay changes flow in either direction, and compliance tooling receives rosters and access data automatically.

Contractor payments in local currency are a payment rail rather than an integration: more than 150 countries on the homepage and more than 200 on the pricing page, a disagreement between the vendor's own pages.

Sourcewarp.co/pricing Integrations matrix and warp.co homepageread 2026-09-12

Warp's agents own processes end to end, and the vendor publishes the stages. The tax notice workflow is a numbered sequence: 01 Notice arrives, "Warp ingests it the moment it appears, no inbox to watch"; 02 Research and triage, "the agent reads the notice, opens the state account, and investigates what actually changed"; 03 Resolution generated, "Warp reconciles the numbers and drafts the response, filed and audit-ready". The stages span two systems and an external counterparty, with a branch at triage and a final write to a government agency.

Hiring is the second workflow, and it spans more systems. Hiring in a new state has Warp identify every required state agency, submit the registrations, hold the credentials and begin filing on schedule, while onboarding provisions SSO, devices and application access the moment someone joins; the published example creates a Google Workspace mailbox, a Slack account and a GitHub account and installs the MDM agent from one new hire event. Offboarding revokes all of it on departure.

State carries across long running work. Registrations sit in Active, Filing started, Awaiting state or Needs info, so a process can wait on a third party for days and resume; twenty eight of thirty four states registered is a tracked total across dozens of flows running at once. The participants are distinct: the agent, the state agency answering on its own schedule, the employee completing onboarding through a self service portal, and the administrator, asked only when something is blocked. Payroll runs on schedule across semi monthly, monthly and off cycle bonus cycles with autopay.

Sourcewarp.co homepage compliance workflow and IT management sectionsread 2026-09-12

The agents ground on a regulatory corpus Warp keeps current. They "monitor 10,000+ jurisdictions", covering federal, state and local tax rules across all fifty states, and update withholding calculations and filing requirements when rules change. Coverage of that size cannot be assembled at request time; it is an index someone maintains, and maintaining it is the product. Warp publishes state payroll tax guides from the same body of knowledge.

The corpus drives filings, not just answers. The agent reads an incoming notice, checks what the rule now says, reconciles against the customer's own payroll data and drafts a response. The homepage example shows it: a CA EDD notice flagging an outdated SUI rate, with the agent identifying the change from 3.4% to 1.5% and applying it to 33 employees. A wrong lookup would file a wrong return.

The customer's own data is the second source, queried alongside: employee records, prior filings, registration state per jurisdiction and benefits enrollment, which is how the agent can verify employee tax rates before proposing a change. No citation behavior, customer facing search over the corpus, document ingestion path or way to add the customer's own policy content is documented. The corpus is Warp's, used internally by the agents, and a buyer cannot inspect or extend it.

Sourcewarp.co homepage compliance section and tax compliance product entryread 2026-09-12

Warp markets the absence of human oversight as the product. The homepage's first named differentiator reads: "Warp's agents own entire workflows: opening state tax accounts the moment you hire, resolving notices, and reconciling benefits without a human in the loop. Every task that used to require manual admin work is handled automatically."

The compliance section repeats it: "Warp AI agents handle tax notices end-to-end, without human intervention." The second differentiator, headed No manual.gov work, says every account is opened, every return filed and every notice resolved. The positioning line is "HR and payroll engineered to disappear".

No gate of any kind is documented: no approval step, confidence threshold, review queue, autonomy setting, escalation policy or hold before filing appears on the homepage, the pricing matrix of roughly seventy line items, or the product pages. The Security and Access section lists 2FA, SSO and role based access control, which govern who may use the platform, not what the agent submits. Expense approvals route employee expense claims, a human process, not oversight of the agent.

The counterparty is a state tax agency and the artifact is a legally binding return. The compliance dashboard does show registrations marked Needs info and a notice card reading Action needed, but that is the agent stopping when it lacks an input and asking for it, not a person reviewing what the agent proposes to do.

Sourcewarp.co homepage and /pricing feature matrixread 2026-09-12

SOC 2 Type II is in place, independently audited across security, availability and confidentiality, with the AICPA mark in the footer of every page linking to a trust portal at trust.joinwarp.com, on the company's other domain, and a security page at warp.co/security.

The customer facing controls depend on the plan. Two factor authentication ships on every tier; single sign on and role based access control start at Pro; Enterprise adds "Security reviews (SOC 2, questionnaires)" and "custom onboarding and security reviews". Underneath sit AES-256 at rest, TLS 1.2 or higher in transit, round the clock monitoring through Oneleet, and BAAs for HIPAA regulated enterprises. A Starter customer gets 2FA but not SSO or RBAC.

The access lifecycle is itself a product: Warp provisions SSO, devices and application access the moment someone joins and revokes them the moment they leave, with Okta and Google Workspace provisioning and MDM sold as the Warp IT add on. That is the customer's own joiner, mover and leaver control, operated by the platform.

No ISO certification, subprocessor list or penetration test statement is published on warp.co, and the state agency credentials the agents hold in order to file have no documented handling or rotation policy, a real gap given what they unlock.

Sourcewarp.co/security as linked, the footer SOC 2 badge and trust portal link, and /pricing Security and Access matrixread 2026-09-12

An audit log with a stated retention period is kept, and the agent's actions are logged at the point of filing. The pricing page lists "Audit logs (30-day retention)" among Starter inclusions and "1-year audit log retention" on Enterprise, and the comparison matrix shows 30 day, 30 day and one year retention across the three tiers under Compliance and Tax.

The compliance workflow's third step reads: "Warp reconciles the numbers and drafts the response, filed and audit-ready, with every action logged." For agents that file legally binding returns with a government counterparty, that record is the control that matters.

The product also shows the agent working. The dashboard displays each step: acknowledging the notice, reading the named PDF, verifying employee tax rates, and stating the rate change from 3.4% to 1.5% for 33 employees, so a reader follows the reasoning rather than only the outcome. Prebuilt reporting and payroll journals ship on every tier, with advanced and custom HR reporting from Pro. The compliance view tracks each registration by status (active, filing started, awaiting state, needs info), so the estate can be inspected per jurisdiction.

No export format, field list or API endpoint for the audit log is published, and 30 days is short retention for a payroll filing record on the entry tier.

Sourcewarp.co/pricing feature matrix and warp.co homepage compliance workflowread 2026-09-12

No agent memory is documented. Durable state accumulates in the platform, including employee records, agency credentials stored in the dashboard, filing history and benefits enrollment, and agents read it on every run, but that is the system of record rather than an agent memory layer.

The vendor lists what it holds: employee profiles and directory, document storage, PTO balances and accrual policies, benefits enrollment and carrier state, expense records, state tax registrations tracked per jurisdiction, filing history, and stored agency credentials. Warp calls this employee management: a record of the company, not of the agent.

The pieces that look closest are something else. Filing history and the audit log, with 30 day and one year retention tiers, record what the agent did. The regulatory corpus across more than 10,000 jurisdictions is the knowledge layer. Stored agency credentials are an access artifact.

Across the homepage, a pricing matrix of roughly seventy line items and six product pages there is no named memory component, no retained preference or correction the agents reapply on the next notice, no decision trace carried from one filing to the next, no stated scope or lifetime for anything an agent holds, and no surface to inspect, edit, export or purge agent state apart from the payroll records.

Sourcewarp.co/pricing feature matrix and warp.co homepageread 2026-09-12

Hosting is multi tenant SaaS with no named region, no residency commitment and no customer environment. The pricing page publishes a comparison matrix of roughly seventy line items across three tiers, grouped under Payroll, Compliance and Tax, Team and Contractors, Benefits, Expense Management, PTO, HR Tools, Integrations, Security and Access, and Support.

It itemizes audit log retention in days and years, separates next day from same day payroll, and prices device management apart from application provisioning, yet has no region, residency, hosting or data location row at any tier, including Enterprise, where "custom SLAs and uptime guarantees" and "custom onboarding and security reviews" are the differentiators. The homepage and the security page name no hosting location either. No self hosting, hybrid, single tenant or bring your own cloud option appears.

Global coverage is a payment rail, not a hosting region. Warp pays contractors in more than 150 countries per the homepage and more than 200 per the pricing page, in local currency at near Google FX rates; paying someone in a country says nothing about where their record is stored. The two country figures disagree between the vendor's own pages.

This matters for buyers. The platform holds payroll and personal data for employees across all fifty states and contractors worldwide, including EEA, UK and Swiss data subjects per the company's own AI readable description, and publishes no residency position. A buyer with a localization obligation has nothing to work from.

Sourcewarp.co/pricing feature matrix and warp.co homepageread 2026-09-12

Warp ships agents for named jobs; the customer does not author them. Five are documented: state tax agency registration, which identifies every required agency on a hire and opens the accounts; tax notice triage and resolution, listed on the pricing matrix as "AI tax-notice auto-resolution"; benefits reconciliation and carrier administration, with enrollment and carrier sync run in house; onboarding with application and device provisioning; and offboarding with access revocation. Each runs as a defined workflow out of the box; the buyer turns it on rather than composing it.

They are separate agents, not stages of one pipeline. Remove benefits reconciliation and tax notice resolution is untouched; remove offboarding revocation and state registration still works. They share a data layer and serve different buyers inside one company: finance cares about filings, IT about provisioning.

The pricing makes them selectable. AI tax notice auto resolution is a Pro line item absent from Starter, and the provisioning agents are sold as the Warp IT add on at $15 per person per month, or separately as Google Workspace provisioning, Okta and application provisioning, and MDM at $5, $5 and $10. A buyer chooses among them and pays per choice. No catalog page, template library, agent builder for customers or third party contribution path appears; the set is supplied by Warp and fixed.

Sourcewarp.co/pricing feature matrix and add-ons block, with the homepage product sectionsread 2026-09-12

Four kinds of event start work, each with a named result. A hire triggers state tax account registration and, separately, application and device provisioning; the published example fires Google Workspace, Slack, GitHub and MDM installation from one new hire event. A departure triggers access revocation, pulled the moment the worker leaves.

An inbound tax notice triggers ingestion, triage and resolution, with no one watching for it: "Warp ingests it the moment it appears, no inbox to watch." And regulatory change is itself a trigger: agents "monitor 10,000+ jurisdictions" and update withholding calculations and filing requirements when rules change.

Schedules are a separate mechanism, visible in the product. Payroll runs semi monthly, monthly and off cycle with autopay, filings follow each jurisdiction's statutory schedule, and the dashboard shows upcoming runs and calendar events. The customer does not set the filing deadlines.

Channels are adequate rather than broad: the admin dashboard, Slack notifications and integration, email, and an employee self service portal where new hires complete tax forms, direct deposit and benefits enrollment before their first day. Expenses accept Slack and email invoice submission from Pro. There is no voice or ticketing channel and none is claimed; the user is a finance or HR administrator watching a queue.

Sourcewarp.co homepage compliance and IT sections, with /pricing feature matrixread 2026-09-12

No model, provider or routing choice is documented anywhere. The pricing matrix of roughly seventy line items across three tiers itemizes the platform down to audit log retention windows, geo fencing on time tracking and per device versus per employee MDM pricing, and has no model row, provider name, routing option or bring your own key path at any tier, including Enterprise. The homepage names the agents repeatedly and never names what runs them.

MCP integration for Claude and ChatGPT, listed on the pricing page, is not model choice. It is the customer's own assistant calling Warp through Warp's MCP server; driving Warp from Claude does not choose the model that reads a tax notice. Nothing says Warp routes across more than one model internally either.

The name needs care. warp.dev is an unrelated company, an AI terminal for developers, which does ship models a customer selects and bring your own key; that capability is its own. This is Warp at warp.co, an AI native payroll and employee management platform.

Sourcewarp.co/pricing feature matrix and API block, with the homepageread 2026-09-12

A REST API, a CLI and an MCP server are all published, and all three are priced. The homepage carries a Warp API block, "Public API for payroll data, reporting, and compliance operations. Build custom workflows and integrate with your existing stack", linking to developer documentation at docs.warp.co.

The Starter tier includes "REST API, CLI, and MCP integration" as one line item, and a dedicated pricing block headed API, CLI and MCP, marked free on Starter and Pro, lists "REST API and CLI tooling included, MCP integration for Claude and ChatGPT, Enterprise API module with lifecycle webhooks, enterprise uptime SLAs, higher rate limits, and dedicated support". Enterprise adds the Enterprise API module with webhooks, SLAs and higher limits.

So the platform can be called over REST, driven from a terminal, subscribed to by webhook and reached from an outside assistant. The API covers payroll data, reporting and compliance operations, which implies the MCP server reads and writes too, and it is offered on the entry tier rather than held back for Enterprise. A CLI alongside the REST API points to a developer audience Warp expects to serve.

This is Warp at warp.co, the payroll platform. warp.dev is an unrelated company, an AI terminal for developers, and its developer tooling is not Warp's.

Sourcewarp.co/pricing API block and feature matrix, with the homepage Warp API block linking docs.warp.coread 2026-09-12

Nothing puts a change under test. No test environment, sandbox, dry run, holdout, versioning of agent behavior, evaluator or scored comparison appears on the homepage, the product pages or a pricing matrix of roughly seventy line items across three tiers. Nothing says a changed filing rule, a new jurisdiction or an updated withholding calculation is tried against known cases before it reaches a live return, and no accuracy rate, resolution quality score, exception rate or drift indicator is shown to the customer.

The outcome figures are vendor reported results, not evaluation tools. "80% of tax notices resolved instantly" and "$100M+ in penalties saved for customers so far" describe aggregate outcomes across a customer base, not whether a given agent behaves correctly, and no buyer can run them. Customer story figures such as 100% compliance across all states are the same kind of claim. Per notice reasoning and the action log are records of what happened, not measurements.

The agents file legally binding returns with state tax agencies without a person in the loop, so a buyer has neither an approval gate nor a published evaluation surface through which to gain confidence in a filing before it is made. That is a coherent product bet.

Sourcewarp.co/pricing feature matrix and warp.co homepageread 2026-09-12

The outcome points at computer use, but Warp never says how its agents reach state agencies. Warp says its agents open state tax accounts, submit registrations and file returns so the customer will "never log into a.gov portal", and the notice workflow says "the agent reads the notice, opens the state account, and investigates what actually changed". Opening a state account is something a person normally does in a browser, and Warp holds agency credentials in the dashboard, which a session based approach would need. That is suggestive, not evidence.

State revenue agencies can be reached several ways: browser portals, bulk filing APIs, EDI and SFTP transmission, and third party filing aggregators, and a payroll provider at this scale plausibly uses all of them depending on the jurisdiction. Nothing published says which. Never logging into a.gov portal is a promise about the customer's experience, not a statement of architecture, so whether the agent would break when a state portal changes its interface cannot be judged from what is published.

No hosted browser, desktop session, remote computer control or RPA appears anywhere in a pricing matrix of roughly seventy line items. The MDM agent installs on employee devices for device management, which is endpoint administration, not computer use.

Sourcewarp.co homepage compliance workflow and /pricing feature matrixread 2026-09-12