Back to app
Platform, stack, and integrations

Platform, stack, and integrations

What Vertiqa is built on, exactly which integrations are shipped today, and an honest read on the gaps a technical evaluator will probe — Outlook, a public API, and webhooks.

Reviewed AdminVertiqa 1.61+

For a technical evaluator, the stack and integration questions are partly a proxy for "will this company survive." Confidence matters more than detail.

The stack, in one sentence

Modern managed cloud: a Next.js front end, a C# API core, a Python agent runtime, and Postgres. Nothing exotic to maintain, all on managed infrastructure. That's the whole answer a client needs — resist over-sharing architecture internals.

Integrations shipped today

  • Calendar, two-way — Google, Zoho, and Apple / iCloud (CalDAV). Availability reads and event writes both directions.
  • Google sign-in for authentication.
  • Email send with branded templates and attachments — outbound email carries the organization's branding, and can include files.
  • Public booking pages that issue .ics calendar invites.
  • Embeddable intake forms you can drop into a client's own site.
  • Voice dictation for capturing notes and updates by speaking.

Gaps to name honestly

A technical buyer will probe these. Name them plainly:

  • Outlook / Microsoft 365 calendar — not shipped, no date. Calendar sync is Google, Zoho, and Apple only today.
  • No public / partner-facing REST API and no outbound webhooks. The platform is API-first internally, but there is no supported, documented external API surface yet. The useful reframe: "which client system would you need to reach?" — that turns a gap into a discovery question instead of a dead end.

The MCP surface — for a technical audience

Vertiqa runs an MCP server — its AI-integration surface, letting AI tools work with Vertiqa data through a structured tool interface. It's worth mentioning to a technical audience as a forward-looking differentiator, framed exactly that way: our AI-integration surface, not a general-purpose public API. Don't let it be mistaken for the partner REST API described above — they're different things.

Was this helpful?