Both. Veryfi started as an API-first platform, built for engineering teams who want to plug document processing directly into their own applications, workflows, and tech stacks. If you have developers, you can be up and running in a day. It's RESTful, well-documented, and built to handle serious document volume.
But not every company that needs document processing has a dev team standing by to build an integration. Veryfi also ships as a full software product - a web dashboard and mobile apps that non-technical teams can use out of the box, no engineering required.
Here's how different teams typically use it:
Developers and engineering teams integrate via the API, embedding Veryfi's extraction and fraud detection capabilities directly into their own products or internal tools
Finance and ops teams log into the web dashboard to manage documents, review extracted data, set up approval workflows, and run reports without writing a single line of code
Field teams and employees use the Veryfi mobile app to capture receipts and expenses on the go, with data syncing automatically into whatever system sits behind it
ISVs and SaaS companies build Veryfi into their own platforms and offer the functionality to their end users under their own brand
And for teams already using existing tools:
Veryfi connects natively with QuickBooks, Xero, and several major ERPs, so the data flows straight into the systems finance teams are already working in. No manual export, no reformatting, no extra step in between.
The short answer is: it depends on your team. Some companies use just the API. Some use just the dashboard. A lot use both. Veryfi is flexible enough to fit however you actually work.