Platform Development

Own your platform,
then build your own apps on it.

A multi-tenant platform for software and business entities. Subscribe to it for your business and run on rails we maintain — or purchase it outright and develop on it yourself, on your own infrastructure, at your own pace.

Two ways to take it

The same platform, two relationships. Start on one and move to the other when it suits the business.

Subscribe

Use the platform for your business. You get the apps, the tenancy, the auth, the billing, the jobs and the storage — and the upgrades. We run it.

  • Turn on the apps you need, per user where that fits
  • Your data isolated in its own tenancy from day one
  • Sign-in, permissions and billing already wired
  • Upgrades and operations handled on our side
  • Add your own apps on the same rails when you're ready
Talk to us →

Purchase outright

Buy the platform and develop it on your own. Your code, your infrastructure, your roadmap — and no per-seat rent on the thing you own.

  • The full source, not an API against someone else's product
  • Runs on infrastructure you choose and control
  • Your roadmap decides what gets built and when
  • No per-seat rent as your headcount grows
  • Bring us back in for build work only when you want it
Talk to us →

Every feature is an app

The platform isn't one monolithic product with a settings screen. Each capability is a discrete app, and that is what makes it something you can develop on rather than merely configure.

Subscribe to what you actually use

Each feature of the platform is its own app, and a tenant subscribes to the apps it wants — per user where that makes sense. Nobody pays for surface area they never open, and nobody sees a screen that isn't theirs.

A new app registers itself

New apps start from a template and register themselves with the platform. That means a brand-new app inherits the login, the tenancy, the permissions and the application shell on day one — not after a month of plumbing.

Your apps ride the same rails as ours

There is no privileged internal path. The apps we build sit on exactly the rails your team builds on, so anything we can ship on the platform, you can ship on the platform.

What you inherit on day one

The parts every serious business application needs, already built, already wired together, already carrying the tenancy model through them.

Enterprise sign-in

Company sign-in and single sign-on, with the user directory and access rules behind it.

Data isolation

Multi-tenant separation enforced at the data layer, so one customer's records can't reach another's.

Billing and subscriptions

Plans, subscriptions and per-user access, tied to the apps a tenant actually turned on.

Background jobs

Scheduled and event-driven work that runs reliably outside the request, with retries and history.

Document storage

Upload, storage and ingestion, so documents become searchable business data rather than dead files.

Mobile

Field and tablet applications built against the same platform, for work that happens away from a desk.

An agent fleet

Autonomous build teams that develop on the platform continuously, reviewing each other's work before it ships.

That's the business-language summary. The full technical picture — 54 services in production across 12 disciplines — has its own page: see the service map →

Build with the fleet

Work on this platform is itself built by agent teams: the plan is decomposed into cases, the cases are dispatched to autonomous agents, and nothing merges until it passes review. The platform is the proof that the machine works — and that same machine is available to platform customers, whether you subscribe or own outright.

How the agent fleet works →

Grotap Platform & Apps · Service Map

Enterprise infrastructure,
behind one login.

Grotap is the cloud in the middle: your apps, your tenant, your data. Around it sits the same infrastructure the largest software companies run on — 54 vetted services, each chosen for one job and paid for by us, so members get enterprise capability without enterprise procurement.

54Services in production
12Disciplines covered
1Platform to learn
0Contracts you sign
signs everyone inkeeps every rowbills and reconcilesruns the long jobsholds the filesruns the servicesdoes the thinkingreaches your peopleguards the doorsships the codedraws the screensscans and prints on siteGROTAPPlatform & AppsIDENTITY & ACCESSTENANT DATAMONEY & BOOKSSBIBACKGROUND WORKFILES & BACKUPCLOUD & NETWORK+3AI & AGENTS+1MESSAGINGSECURITY & TRUSTAVBUILD & RELEASEINTERFACEOWFIELD HARDWARECSL+1
Every line is a live dependency of the platform. The centre is ours; the twelve groups around it are the outside services Grotap holds the accounts, keys and bills for.

SIGNS EVERYONE IN · 2 services

Identity & Access

Who you are, which company you belong to, and what you are allowed to open. Every request into the platform carries an answer to those three questions before it touches data.

WorkOS logo

WorkOS

  • Issues the signed token behind every session and resolves it to your organisation, your role and your app permissions.
  • Single sign-on, directory sync and SCIM provisioning arrive as a product feature instead of a six-month build, so an enterprise member can plug in Okta or Entra on day one.

Google Identity

  • Runs the consent screen when you connect a Google mailbox, calendar or Drive folder to the Loop Engine.
  • Access is granted by you, scoped to what the feature needs and revocable from your own Google account. We never hold a password.

KEEPS EVERY ROW · 3 services

Tenant Data

Your operational record: items, scans, quotes, jobs, history. Separation between tenants is enforced by the database itself, not by application code remembering to filter.

Neon logo

Neon

  • Serverless Postgres for the control plane and for every tenant: pooled shards under forced row-level security, or a dedicated database for members who want their data physically apart.
  • A new tenant database is provisioned through an API call in seconds, and branches give us a full copy of production data to test a migration against before it runs for real.

Redis

  • Shared memory across every running copy of the backend: rate limits, hot caches and spend guards.
  • Limits stay correct when traffic scales across replicas, so one noisy integration cannot degrade the platform for everyone else.
Microsoft SQL Server logo

Microsoft SQL Server

  • Read by an on-premises bridge that connects to an existing ERP database sitting on your own network.
  • Members running older systems with no public API still get their data into the platform, without opening that server to the internet.

BILLS AND RECONCILES · 4 services

Money & Books

Subscriptions, invoices and the accounting systems our members already close their month in.

Stripe

  • Runs subscriptions, usage invoicing, card payments and the payout split for apps built by third-party creators.
  • Card data never touches our servers. PCI scope, tax calculation, dunning and receipts are Stripe’s problem, which is exactly where that risk belongs.

QuickBooks Online

  • Two-way sync between ScanTap activity and the books: customers, items, invoices.
  • Most members already close their month in QuickBooks. Syncing beats re-keying the same numbers twice and getting two different answers.

Oracle NetSuite

  • Signed API access into a member’s NetSuite account for reading orders, items and inventory.
  • Larger members keep NetSuite as their system of record while the platform owns the RFID and field layer on top.

SBI Software

  • Read-only gateway into SBI Grower, the ERP the nursery and grower industry already runs on.
  • Integration is read-only by design: the platform can see stock and orders, and cannot corrupt the system the business depends on.

RUNS THE LONG JOBS · 1 service

Background Work

Everything that must finish reliably minutes or hours after you clicked: ingestion, scheduled loops, webhook fan-out.

Inngest logo

Inngest

  • Durable step functions behind document ingestion, mailbox polling, payment webhooks and every scheduled routine, with live progress reported back to the screen.
  • Each step is retried on its own and picks up where it failed, and work is prioritised and throttled per tenant, so a large import for one member never starves another.

HOLDS THE FILES · 2 services

Files & Backup

Documents, photographs, label artwork, camera frames and session media, plus the copy that exists in case everything else is gone.

Cloudflare R2

  • Object storage for uploaded documents, support media, print-camera frames and public assets, with automatic expiry on the short-lived ones.
  • Zero egress fees mean video, replays and image-heavy features stay affordable to actually use, rather than being rationed to protect a bandwidth bill.

Wasabi

  • Nightly encrypted database dumps copied off-platform, in a second region, on a second provider.
  • A disaster that takes out our primary cloud cannot also take out the backups. The copy is somewhere with no shared failure mode.

RUNS THE SERVICES · 9 services

Cloud & Network

The machines, the edge in front of them and the code that rebuilds all of it from scratch.

Railway

  • Hosts the API and every worker service behind api.grotap.com, with health checks and instant rollback.
  • Container-to-production deploys without a Kubernetes team, so engineering effort goes into member features instead of cluster maintenance.

Vercel

  • Serves the web application and the marketing site from the edge, and provisions a branded subdomain per member.
  • The application loads fast anywhere in the world, and a white-label domain is a settings change rather than a support ticket.

Cloudflare

  • DNS, CDN and web application firewall for every domain; Zero Trust access on internal tools; Turnstile against bots on public forms; TURN relay for live support sessions.
  • Denial-of-service defence and bot filtering sit at the network edge, absorbing attacks long before they reach an application server.

Hetzner

  • Dedicated servers running the build fleet, the self-hosted tool stack and GPU inference.
  • Roughly a fifth of the per-core cost of the large US clouds, which is what makes a continuously running engineering fleet economically possible at all.

Tailscale

  • Private mesh network reaching RFID readers and edge devices that live inside a member’s own building.
  • Hardware on site is reachable for updates and diagnostics with no inbound firewall holes and no port forwarding on your network.

Caddy

  • Reverse proxy in front of every self-hosted service, terminating TLS.
  • One place where routing and encryption are configured, and nothing is ever exposed without it.

Let’s Encrypt

  • Issues and renews the TLS certificates on every hostname we run.
  • Certificates renew automatically, so an expired certificate can never take a member-facing service offline.

Docker

  • Packages each service as one image that runs identically on the cloud, on our servers and on a member’s PC.
  • What passed testing is exactly what runs in production. There is no "works on my machine" gap to debug at 2am.

Terraform

  • Declares every server, network and firewall rule as reviewed code.
  • Infrastructure can be rebuilt exactly, audited like software, and no change is made by somebody clicking through a console at midnight.

DOES THE THINKING · 7 services

AI & Agents

The models behind in-app assistance, document understanding and the agent fleet that builds and reviews the platform itself.

Anthropic

  • Claude is the default model for in-product assistance and for every engineering agent, including the review pass that gates code before release.
  • Strongest available model for reasoning over code and tools. The quality of the platform’s own build pipeline depends directly on it.

OpenAI

  • Embeddings that make your documents searchable by meaning, and transcription for voice notes and calls.
  • Specialised, inexpensive models for the high-volume jobs, keeping the expensive reasoning model for work that needs it.
OpenRouter logo

OpenRouter

  • A single gateway to the open-weight model catalogue, used for lower-cost and experimental routing.
  • Models can be swapped by configuration rather than a code change, so no single AI vendor can hold the platform hostage on price.

LangChain

  • LangGraph runs multi-step agent workflows with state checkpointed to Postgres; LangSmith traces every run and its cost.
  • A crashed or interrupted agent resumes instead of starting over, and every automated decision has a trace we can inspect after the fact.
PageIndex logo

PageIndex

  • Builds a reasoning index over long structured documents such as manuals, contracts and specifications.
  • Answers cite the right section of a 400-page document instead of returning a plausible paragraph from the wrong chapter.
vLLM logo

vLLM

  • Serves open models on our own RTX PRO 6000 GPU for private and high-volume inference.
  • Sensitive tenant content can be processed without leaving hardware we own, and heavy batch work runs at fixed cost.

Ollama

  • Local model runtime on development machines and as a fallback endpoint.
  • Engineering work on AI features continues even when an external provider is degraded.

REACHES YOUR PEOPLE · 4 services

Messaging

How the platform talks to your staff, your customers and your inbox.

Twilio

  • SMS notifications with delivery receipts, and in-browser voice calling for support.
  • Carrier-grade routing and number compliance in every region we operate, which is not something any platform should try to own.

Resend

  • Transactional email: invitations, alerts, receipts, password flows.
  • Deliverability is managed properly with signed sending domains, so the mail that matters reaches the inbox and not the spam folder.

Slack

  • Operational alerts pushed into the channel your team already watches.
  • Incidents surface where people are, instead of in a dashboard nobody has open at the time.

Google Workspace

  • Gmail, Drive, Sheets and Calendar APIs behind the Loop Engine, document sourcing and availability automation.
  • The platform meets your documents and mail where they already live rather than demanding everything be re-uploaded.

GUARDS THE DOORS · 4 services

Security & Trust

Uploads, secrets and sessions are treated as hostile until proven otherwise.

ClamAV

  • Every uploaded file is scanned for malware by a scanner we run ourselves, and an upload that cannot be scanned is refused.
  • Members can exchange files without the platform becoming the delivery mechanism for someone else’s infection, and those files never leave our infrastructure to be checked.
GitGuardian logo

GitGuardian

  • Watches every commit for credentials that should never have been written down.
  • A leaked key is caught at the commit, not months later in an incident report.
OpenReplay logo

OpenReplay

  • Self-hosted session replay and live co-browsing, so support can see the screen you are describing.
  • Running it ourselves means recordings of your business stay on our infrastructure and are not sold on as analytics.

VirusTotal

standby
  • Multi-engine second opinion on suspicious files.
  • Held in reserve as a standby scanner if the primary scanner is unavailable.

SHIPS THE CODE · 5 services

Build & Release

How a change gets from a keystroke to your screen, and what stops a bad one on the way.

Doppler logo

Doppler

  • The single home for every credential the platform uses, injected at run time into the cloud, the build system and the fleet.
  • No secret is ever stored in the codebase or pasted into a dashboard, and one rotation reaches every service at once.

GitHub

  • Source of truth for the code, plus the automated checks, tests and deployments that run on every change.
  • Nothing reaches production without passing the same recorded, reviewable gate.

Forgejo

  • A second, self-hosted copy of every repository with its own build runners, mirrored continuously.
  • An outage or policy change at a single vendor cannot stop us shipping a fix you are waiting on.

Expo

  • Builds and releases the mobile applications for Android and iOS.
  • Mobile ships on the same cadence as the web, without a separate native build lab.
Playwright logo

Playwright

  • Drives a real browser through the critical journeys before release, and powers automated in-app tasks.
  • Regressions are found by a machine walking the actual product, not by a member reporting it on Monday.

DRAWS THE SCREENS · 6 services

Interface

What the work actually looks like: grids, editors, maps and the shell every app in the catalogue is built inside.

AG Grid logo

AG Grid Enterprise

  • The licensed data grid behind inventory, scans and admin tables, with grouping, pivoting, filtering and Excel-grade export.
  • Members get spreadsheet-class control over their own data inside the product, without exporting it somewhere else first.

Mantine

  • The component system and application shell every app in the catalogue is required to use.
  • Every app looks and behaves like part of one product, and accessibility is inherited rather than re-litigated per screen.
Tiptap logo

Tiptap

  • The rich-text editor used for notes, specifications and playbooks.
  • Structured documents keep their formatting through storage, search and export.

Leaflet

  • Renders the interactive maps for road networks, tag locations and field routes.
  • A mapping layer we control, with no per-view billing meter running while a crew works.

OpenStreetMap

  • Supplies the map tiles underneath those views.
  • Open map data with no licence key and no per-load charge, so field mapping scales with usage instead of budget.

OpenWeatherMap

  • Live and forecast weather feeding the weather-dependent scheduling features.
  • Field work is planned against real conditions rather than a guess.

SCANS AND PRINTS ON SITE · 7 services

Field Hardware

The equipment in the yard, the greenhouse and the print room, managed from the same platform as everything else.

Toshiba TEC

  • The industrial B-EX RFID label printers: label layout, encoding, darkness and speed all driven remotely by Print Cloud.
  • A label is designed once in the browser and printed identically on every printer, with settings verified from here rather than at the machine.

CSL

  • Convergence Systems CS463 fixed RFID readers doing the actual tag capture.
  • Industrial-grade readers with an open control protocol, so they are configured and monitored from the platform instead of a vendor utility.

Raspberry Pi

  • The rugged edge unit running the reader loop next to the equipment.
  • Scanning continues through a network outage and syncs when the connection returns, so no counts are lost.
Headwind MDM logo

Headwind MDM

  • Self-hosted device management for the field tablets: enrolment by QR code, silent application updates, remote lock and reboot.
  • No per-device licence fee, so a member can add tablets as the crew grows instead of budgeting for each one.

Wyze

  • Inexpensive cameras watching the label printer during a production run.
  • A print-quality problem is diagnosed by looking at it, rather than by sending somebody to site.
MediaMTX logo

MediaMTX

  • Streams that camera feed out of a private network to the support view.
  • Live video from a member’s floor with no inbound connection into their network.
coturn logo

coturn

  • Our own relay that connects live video and voice sessions through restrictive networks.
  • Support calls connect from behind any corporate firewall, with no per-minute relay charge.

Evaluated and replaced

Things deliberately not on the map. A stack is also the list of what was tried and dropped.

  • Cobrowse.ioReplaced by self-hosted OpenReplay, so session data now stays on our own infrastructure.
  • Auth0Evaluated for authentication; WorkOS was chosen for its directory and SCIM support.
  • MongoDBEvaluated against Postgres for tenant data; Neon won on isolation and branching.
  • Headwind hosted tierRetired at a three-device cap in favour of our self-hosted server, which has none.
  • Impinj SpeedwayAssessed as an alternative RFID reader; the CS463 was retained.
  • Neon MCP serverRetired in favour of direct, credential-injected database access.
Grotap Platform & Apps Service map, September 2026 Logos are the property of their respective owners

Let's talk about which one fits

Tell us the business, the users and where you want to own the code. We'll tell you straight whether subscribing or purchasing outright is the better deal for you.

No obligation — we'd rather scope it honestly than sell you the wrong shape.