Integration marketplace · Every integration starts from a blank page.

A working integration, installed from a catalogue.

The in-app marketplace holds packaged integrations you install rather than build: systems, mappings, workflows, reports and portal pages, free and premium. STRAX screens every listing and a person at STRAX approves it before it goes live. You can also package what you built and sell it.

Request a demo → Browse the catalogue All features → How the marketplace works →

A working integration from the catalogue

The in-app catalogue holds packaged configurations (systems, tables, mappings, queries, workflows, reports, report themes and portals) that install in an afternoon rather than weeks. The same catalogue is browsable on this site, and installs happen from inside STRAX. Connector types themselves ship as bundles, and so do report themes: the Report Themes Starter Pack holds four ready-made looks, each theme carries its logo and images inside the package, and you customise your own copy of an installed theme.

Live Feature Marketplace → your installation Install · screened · approved
Installing a marketplace bundle into STRAX A listing is installed from the Feature Marketplace; its tables, queries, reports, workflow and site appear in the installation one after another. Feature Marketplace Browse · preview · install Customer onboarding kit Signup portal, approvals, reporting 4 tables 3 queries 2 reports 1 workflow 1 site ✓ Screened: no executable steps, no secrets Install Field-ops dashboardFree Billing sync · SplynxPremium Your STRAX installation On your servers · nothing runs before you approve it Tables 4 hub tables Queries 3 saved queries Reports 2 PDF reports Workflow approval flow Site signup portal Ready to install Installing 11 artefacts: tables, queries, reports, workflow, site… Installed in 41 s, live on your data, and nothing ran before you approved it. Then, in the same place: Customise with AI Merge into existing Open the portal
Packaged configuration (systems, mappings, queries, workflows, reports and portals) installs in under a minute, screened before anything runs.

From an idea to production in days

If the catalogue does not have what you need, describe it. The AI assistant turns a plain-language brief into a concrete plan of the systems, mappings, workflows, reports and portal pages it needs, then drafts every piece for your review, and nothing is applied until you accept it. The work runs on staging first, with staging data and staging values, and one push moves it to production with the platform's checks on credentials, variables and bindings on the way. What used to be a quarter-long integration project ships in days.

Live Idea → production, with AI assistance Plan · build · stage · push
From idea to production in days The AI assistant plans an integration from a brief, drafts the integration, API, workflow, report and portal, the bundle verifies on staging, and one push takes it live, in days on a timeline where the old way took months. Plan Describe it in plain language AI Assistant Integration plan Systems · mappings · steps · pages Build AI drafts, you review Integration API endpoint Workflow Report Portal site Staging Staging data · staging values Integration API endpoint Workflow Report Portal site Production One push, checks on the way Integration API endpoint Workflow Report Portal site LIVE Day 1 Day 2 Day 3 Day 4 Describe it and the AI assistant plans it. The AI drafts every piece for your review. Verified on staging first. One push and it is live. The old way: a 3–6 month integration project M0 M1 M2 M3 M4 M5 M6 With STRAX live before the first month-mark, in days
Planned by the AI assistant, drafted for review, verified on staging and pushed to production, in days on the calendar.

Screened before it runs

Nothing reaches the catalogue without STRAX approving it. Every submission is screened server-side, then reviewed and approved by someone at STRAX before it is listed. Every package is also scanned for executable steps and embedded secrets, the results are disclosed before you install, and packages carrying executable content require your consent.

  • "Customise with AI" adapts an installed package to your environment in a conversation.
  • "Merge into existing" combines a package with configuration you already have.
  • A guided export builder packages your own configuration for reuse, or for sale through the catalogue.
  • A bundle brings what it needs: the other bundles and code libraries it depends on are listed in one confirmation and installed together, in the right order.
Live Built once, approved, installed anywhere Screened server-side · approved by STRAX
From a reviewed feature to many companies A feature is screened and then approved by STRAX, published as a marketplace listing, and adopted by six companies, each fulfilling its own strategy. Build & STRAX review Submitted by a supplier · screened by STRAX Field-ops dashboard by Acme Integrations · v1.2 2 tables 1 query 1 site No executable steps No embedded secrets Validated against the metadata Newer than the live version APPROVED BY STRAX Quality ✔ Security ✔ Performance ✔ Marketplace Public catalogue · installs from inside STRAX Customer onboarding kit Billing sync · Splynx Ticket escalation flow Field-ops dashboard by Acme Integrations ✓ STRAX approved v1.2 Free Published · installs in minutes Companies The same reviewed feature, fulfilling many strategies Fibre operator Field ops live Clinic network Bookings in one place Retail chain One customer record Property group Tenant portal live Logistics group Dispatch automated Manufacturer Plant data, one view A strategy gap: a field-ops dashboard is needed Companies install the package to close it. Six companies, one review, six strategies served.
Nothing is listed until STRAX has screened it and someone at STRAX has approved it. The same package is then installed wherever it fits, serving a different strategy in each company.

Sell on the marketplace

Register as a supplier, submit listings for review, and track sales in a supplier portal. Your integration know-how becomes a product other STRAX customers can install, and every sale is shared between you and STRAX. Report themes you design are published to the marketplace the same way.

Live Package → list → sell → share Export builder · supplier portal · shared sales
Selling a packaged feature on the marketplace Tables, mappings, queries, a workflow, a report and a site are packaged into one feature, listed on the marketplace, bought by three companies, and every sale is shared between the supplier and STRAX. Your installation Export builder · choose what becomes the product Tables 4 hub tables Mappings 12 field maps Queries 3 saved queries Workflow approval flow Report monthly PDF Site field-ops portal Field-ops dashboard v1.0 Your package · by Acme Integrations Select what to package Packaging 6 artefacts · secrets stripped Packaged · submitted to the marketplace Marketplace Premium listings · licensed per customer Customer onboarding kit Billing sync · Splynx Ticket escalation flow Field-ops dashboard by Acme Integrations Premium ✓ STRAX approved v1.0 Sold by you · a licence key per customer Revenue share Every sale is shared between you and STRAX Fibre operator Installed Clinic network Installed Retail chain Installed Sales ledger No sales yet 1 sale 2 sales 3 sales Your share Paid to you STRAX Platform share Package first, then list it Listed. Every sale is shared with you. Three sales, shared with you and paid out.
The export builder packages what you built into one feature, the marketplace lists it as a premium product, and every sale is shared between you and STRAX and tracked in your supplier portal.

Keep exploring

More in Connect

One hub keeps every system on the same record.

Billing, CRM, provisioning and support all show the same customer, order and asset, updated automatically within seconds and with nothing re-keyed.

Integration engine →

Databases, APIs and a growing list of SaaS profiles.

SQL Server, MySQL and PostgreSQL with change capture, any REST or OpenAPI service, webhooks, and ready-made SaaS profiles from the marketplace.

Connectors →

Your workflows, published as APIs partners can build on.

Partners, customers and your own apps call your workflows as versioned APIs, each caller with its own access and limits and every call logged.

API gateway →

See it on your own systems.

A demo takes about an hour and runs against systems like yours, starting with the ones you would connect first.

Request a demo → Request a quote