Skip to main content

Application Integration Manual

Two different stories:

PathOne-line summary
Marketplace AppMetadata package executed by Qefro Runtime. No backend required.
External SDK ConnectionConnect an existing ERP / POS / CRM with the Qefro SDK over /qefro.
Developer → Create App Metadata → Validate → Package → Publish
→ Install into Workspace → Qefro Runtime

External ERP / POS / CRM → Qefro SDK → /qefro → Qefro Runtime

Do not start from “write a /qefro server to publish a Marketplace App.” That is the external-integration path.

Full comparison: Runtime vs SDK.

Start here

  1. Build your first app — metadata Marketplace App
  2. Runtime vs SDK — which path you are on
  3. Building Applications for Qefro — both paths in one manual
  4. Integration models

Tutorials

TutorialPathReference implementation
Managed Marketplace AppMetadata → Runtimerestaurant-pro-runtime, real-estate-runtime, shopify-runtime (collection)
External SDK ConnectionSDK → /qefroabm-demo, mock-order-status-sdk (Focus / Yaaz / ABM style)
Migration: External → ManagedSDK packagingSame SDK app, different plumbing

Protocol & SDK (external systems)

TopicDoc
SDK application developmentsdk-application-development.md
/qefro protocolqefro-protocol.md
Toolstools.md
Authentication (HMAC)authentication.md
Tenancy & workspacestenancy-and-workspaces.md

Platform capabilities

CapabilityDoc
Managed storagestorage.md · solutions/managed-storage
Customer Hub (ctx.customer)customer-hub.md
Organizationorganization.md
Marketingmarketing.md
Workflows / FlowRunnerworkflows.md · solutions/workflows

Ship & operate

TopicDoc
Deployment (SDK processes)deployment/external-and-managed.md
Marketplace publishingmarketplace-publishing.md
Testingtesting.md
Securitysecurity.md
Troubleshootingtroubleshooting.md

Verified against: Marketplace hosting: runtime packages (restaurant-pro-runtime), @qefro-ai/backend 1.7.0 for the SDK path, protocol version 1.