Apps & Delivery

One definition. Six ways to deliver it.

Build the app once — tables, flows, pages — and publish it as a web app, an installable PWA, a rate-limited API with an OpenAPI spec, a tool set for AI assistants, native push, and an offline-capable client. Same version, same permissions, same audit trail.

The builder Six surfaces API products Mobile, push & offline Ship with discipline
App Builder

Full-stack web apps — no backend required

Build internal tools, dashboards, and authenticated customer-facing applications with a point-and-click builder. Every component connects directly to your workflows and database, and server-side includes run flows inline on page load.

  • Native authentication with login, signup, sessions, TOTP MFA, and SAML single sign-on per application
  • Pre-built components: tables, charts, forms, buttons, file upload — responsive by default
  • Public portals, forms, and websites on custom domains with auto-provisioned certificates and CAPTCHA
  • Compliance built in: consent banners, erasure requests, DSAR exports, and hosted checkout as single HTML tags
  • An embedded, governed AI assistant — text or voice — scoped to the tables you allow
  • Every app gets a managed mailbox and can register its own mail domain with DKIM and SPF
 Customer Portal
3
Open tickets
24
Resolved
🤖 AI Assistant: "How can I help today?"Live
📱 Install app · works offlinePWA
Universal Delivery

Publish once, project to six surfaces

An application's delivery descriptor declares which surfaces it projects. On publish, a deterministic compiler produces every artifact from the same sealed bundle — and a surface that fails to compile never blocks the publish or serves a stale version.

Web

Pages, portals, and forms on your domain, with server-side includes executing flows inline. This site is one.

PWA

Installable on desktop and mobile with a platform-managed service worker and sync client, cached per published version, rolled forward on every deploy.

API

A derived API product with an OpenAPI 3 spec, plans with rate limits and quotas, consumer keys, and metered usage — ready for your developers or your partners'.

Agent tools

The app's flows compiled into a tool manifest for Claude and other assistants, carrying the app's permissions. MCP →

Push

Named notifications declared on the app, delivered natively to iOS (APNs), Android (FCM), and browsers (Web Push) via per-device subscriptions.

Offline

Offline snapshots with conflict-aware sync when connectivity returns, and signed offline licences so an installed app keeps working without the server.

API Management

Your app is an API product, too

Every table and flow is already reachable over REST and OData. API products bundle the endpoints you choose into something you can hand to a partner: a spec, plans, keys, limits, and a usage record for billing.

  • Derived products — enable the API surface and publish generates a draft product and OpenAPI spec; you own it from there
  • Plans with requests-per-second, burst, quota windows, and allowed scopes; many plans per product (Free / Pro / …)
  • Consumers keyed by scoped API tokens; rate limiting enforced at the filter, off the hot path for metering
  • Usage records share one metering pipeline with Marketplace licensing, so billing has a single source of truth
  • Custom-domain API aliasing keeps your brand on the URL
 API Product — Field Service v12
📘 OpenAPI 3 spec · 9 endpointsDerived
Plan: Free · 5 rps · 10k/month2 consumers
Plan: Pro · 50 rps · 1M/month7 consumers
📊 Usage this month: 412,908 callsMetered
Mobile, Push & Offline

Field-ready without a native codebase

Install the PWA, subscribe the device, and the app keeps working in a basement or on a plane. Photos and documents upload in resumable chunks when the connection is back; notifications arrive natively.

  • Device subscriptions record each device's push capability and key material; credentials are account-scoped and isolated
  • Resumable chunked uploads — large files split into content-addressed parts, deduplicated, assembled server-side with bounded memory
  • Offline snapshots per published version, with a sync outcome matrix that resolves conflicts predictably
  • Platform security fixes reach every installed app on the next deploy — the runtime is platform code, the data is app data
  • SMS in both directions with automatic STOP/START handling; bring your own Twilio number
📷 48 MB inspection photo → 12 chunksUploading
📴 Connection lost · 7/12 storedPaused
📶 Back online · resumed from chunk 8Done
🔔 Push: "Inspection 2291 approved"APNs
Govern & Ship

Version control and release management for no-code

No-code shouldn't mean no discipline. FlowClick brings software-grade change management to your workflows and apps — without making anyone learn git.

  • FlowGit — branches, commits, diffs, merges, merge requests, and tags for your applications
  • FlowBuild — change requests, releases, environment promotion with approvals, deployment, and one-click rollback
  • Proposals — changes drafted by an agent or a person are validated against evidence and approved before they promote
  • Version snapshots at app and object level, with diff against published and restore
  • Edit locks, impact analysis before a change, and audit_app rules that flag anti-patterns
  • Portable .hpkg bundles export, import, and share entire applications — never locked in
 Release 2.4 — Pipeline
🔀 CR-118: new approval flowMerged
↓
🧪 Staging — validation passedPromoted
↓
🚀 Production deployAwaiting approval

Publish one app six ways

We'll build a small app in the demo and publish it as a portal, a PWA, an API, and a tool set for Claude — from one definition.

Start Free Trial Schedule a Demo