App Marketplace

Every app your operation needs, in one store.

Browse certified apps, plug-ins and vision model packs built for Docklify. Review exactly what each one can see and do, install it inside your own workspace, and manage versions, access and removal from one place.

Clay-style illustration of an app marketplace storefront: a small shop with a teal signboard, shelves of orange boxes and teal carts in frontClay-style illustration of an app marketplace storefront: a small shop with a teal signboard, shelves of orange boxes and teal carts in front

About this product

Docklify App Marketplace is where the platform grows past what one team can build. It lists certified apps, plug-ins and user-trained small vision models made for Docklify: configuration packs that drop in ready-made reports and templates, integration apps that connect outside systems through the public API, and embedded apps that work inside Docklify pages. Every listing passes a certification review before it appears, every install happens inside your own workspace after you review its permissions, and every version stays pinned until you choose to update. Developers earn 85% of each paid sale, and tenants get the long tail of logistics software — the one report format, the one carrier link, the one check only their operation needs — without waiting on the core product.

What it is for

Who it is for:For tenant admins who extend Docklify, and developers who sell to them.

Tenant admins

Find the missing piece and install it without a project: browse, review permissions, install, and hand it to the right roles.

Operations teams

Close the gaps the core apps leave: a custom report pack, a carrier link, a check that only your floor needs.

Developers and integrators

Sell to every Docklify tenant from one listing: certification, billing and payouts handled by the platform, with 85% of each sale.

3PLs with custom needs

Private apps built for one tenant stay private: your own reports and integrations, installed only in your workspace.

Core workflow

  1. Browse the catalog
  2. Open the app page — permissions, version, ratings
  3. Review scopes and confirm the install
  4. Configure roles and placements
  5. Manage versions, updates and removal

Key features

Clay illustration: a small storefront with three shelves — report packs, integration plugs and vision model boxesClay illustration: a small storefront with three shelves — report packs, integration plugs and vision model boxes

Three kinds of goods

One store, three kinds of goods. Configuration packs bundle reports, document templates, custom fields and flow rules into a single atomic install — no code, no project. Integration apps run on the developer’s own servers and connect through the versioned public API and signed webhooks, so an outside system plugs into Docklify without ever touching its database. Embedded apps work inside Docklify pages through a sandboxed frame. And vision model packs — small, user-trained detection models — list, certify and install through the same mechanism as any other app, so a model that spots a blocked aisle reaches every tenant the same way a report pack does.

Clay illustration: a checklist with a teal check seal stamping a small app box approvedClay illustration: a checklist with a teal check seal stamping a small app box approved

Certified before it lists

Nothing appears in the catalog on a promise. Every app passes a certification checklist before it lists: real implementation, not a slide deck; declared permissions that match what the code actually asks for; a sandbox install that proves the happy path; and a review record kept with the listing. Certification lasts twelve months, and a major version — a scope change, a new endpoint, a new embedded domain — triggers a fresh incremental review. Apps that have not passed stay private: they install only in the tenant they were built for, and never appear in the public catalog.

Clay illustration: a consent card with permission toggles and a worker pressing the confirm buttonClay illustration: a consent card with permission toggles and a worker pressing the confirm button

Install with explicit consent

Installing is a decision, not a click-through. The app page shows exactly what the app may see and do — which data, which scopes, which pages it embeds in — before anything installs, and the public page itself installs nothing: the install opens the App Center inside your own workspace, where you review the same list once more and confirm. Scopes are least-privilege by design, and the four money-and-stock scopes — price, billing, inventory adjustment and refunds — only ever propose; they never write directly. Consent is recorded with the install, so any later question has an answer.

Clay illustration: version pins on a release board, one pinned version glowing teal while a new one waits in lineClay illustration: version pins on a release board, one pinned version glowing teal while a new one waits in line

Versions stay pinned

An update never lands by surprise. Every install pins to the version you approved, and new versions arrive as a choice, not an ambush: staged rollout moves a version tenant by tenant, the certification record follows the version, and the public API carries a deprecation window so an app built against an old version keeps working while its developer catches up. If a version misbehaves, the pinned version is the rollback point — reinstall the known-good build and the workspace is back where it was, with the whole history in the audit log. The developer sees the same rollout state you do, so a question about a version has one answer on both sides.

Clay illustration: a large teal off switch beside a small app box, with a tidy removal checklist underneathClay illustration: a large teal off switch beside a small app box, with a tidy removal checklist underneath

Kill switch and clean removal

Every install has an off switch. If an app misbehaves, the platform or the tenant stops it per tenant, near-instantly — no redeploy, no ticket queue, no waiting for the developer to answer. Uninstalling removes the app’s data from the tenant: configuration copies the tenant never changed are reclaimed, copies the tenant edited stay theirs and are listed in the removal result, and nothing is deleted silently. Consent snapshots and the audit trail stay on file for twenty-four months, so a dispute a year later still has evidence. The switch itself is tiered: stop one tenant, stop a version everywhere, or stop the app outright — each level logged with who pulled it and when.

Clay illustration: five stars above a small storefront, three of them lit teal, with a count badge besideClay illustration: five stars above a small storefront, three of them lit teal, with a count badge beside

Ratings you can trust

The catalog shows what tenants actually think, not what a listing claims. Each organization rates an app once, on a one-to-five scale, with an optional private note that never goes public; there are no public text comments to game. The average appears only once three organizations have rated, shown to one decimal with the count and the star distribution beside it. Install counts never show exact numbers — only bands: under ten, ten-plus, fifty-plus, one hundred-plus, five hundred-plus — so a small app is not punished for being new, and a big number cannot be faked by a single tenant.

Clay illustration: a balance scale with a teal 85 weight and a small orange 15 weight, coins stacked besideClay illustration: a balance scale with a teal 85 weight and a small orange 15 weight, coins stacked beside

Developer economics, 85/15

The split is simple, and it is the industry’s: the developer keeps 85%, the platform keeps 15%. Settlement runs monthly on the net amount — Stripe channel fees and refunds come off first — with a fifty-dollar minimum payout and Stripe Connect transfers, and a refund in one month offsets the next month’s payout instead of disappearing. Tenants pay in dollars, converted from their Credit wallet at one Credit to one cent, and a plug-in fee only ever draws from purchased balance, never from the monthly allowance. The books keep developer receivables, platform share, channel fees and refund offsets in four separate ledgers.

The everyday essentials

L1 configuration packs

Reports, templates, fields and rules as one atomic pack — validated whole, installed whole.

L2 integration apps

Developer-hosted apps that connect through the public API and signed webhooks.

L3 embedded apps

Working pages that run inside Docklify in a sandboxed frame.

Versioned public API

OAuth scopes with server-enforced tenant isolation on every call.

Event and webhook channel

Signed events delivered to apps, with dead-letter handling when delivery fails.

Public gate

The public side stays closed until the platform opens it; private installs always work.

Sandbox for certification

Test installs and review evidence before a listing goes live.

Full audit trail

Installs, consent, version changes and removals — every step recorded.

Ecosystem support

Clay illustration: a small storefront with three shelves — report packs, integration plugs and vision model boxesClay illustration: a small storefront with three shelves — report packs, integration plugs and vision model boxes

Vision model packs

Small vision models publish through the same marketplace mechanism as any other app, and Vision runs and distributes them: the marketplace owns registration, certification, visibility and settlement, while Vision’s detector registry only runs and ships the certified packs to sites and edge boxes.

AI Models

The control room for the small models behind Rollie and Vision: a model library, versions, teaching and validation — every model the platform runs, managed in one place, and the same models that list as vision model packs in the marketplace.

Integration

The connectors and the versioned public API that marketplace integration apps build on: sales channels, ERPs, carriers and EDI, already connected in one flow, so a new integration app starts from working plumbing instead of from zero.

How it connects:Sits on the Integration platform and Admin: listings install into any Docklify app, model packs feed Vision, and every install is governed from the App Center.

Ready to put it to work?

Explore the other apps