Available
Workspace node
A block with inputs and outputs that users drag into their flow. Written in Python or TypeScript.
In the client's Workspace executorSovereign-ready or Connected
Community
Provider program
Bring your service into Emblema.
Models, infrastructure, data, connectors: integrate your product into Workspace and reach the businesses and FDEs that use Emblema.
Who providers are
The people who make Emblema more capable.
A.I. models
Language, vision, voice or generative models that run inside Emblema.
Examples: Industry LLMs, OCR, transcription, image generation
Infrastructure and GPUs
Hardware and services to install Emblema at businesses.
Examples: GPU servers, rental, hosting, on-site support
Data and connectors
Access to the systems where a business's data lives.
Examples: ERP, CRM, document archives, databases
Software and APIs
Products that become a step in a workflow.
Examples: E-signature, invoicing, translation, notifications
Integration
Four ways to integrate.
Every integration declares where it runs: inside the client's network or on your cloud.
Available
Model service
Your model in a container, running on the client's GPUs and used by nodes.
On the client's GPUsSovereign-ready
Available
Workspace template
A complete, ready-to-use flow combining your nodes with Emblema's.
Wherever its nodes runSovereign-ready or Connected
Coming soon
Connector
Connects Workspace to your existing service over an API.
On your cloudConnected
Two tiers
Sovereign-ready or Connected.
Emblema's promise is that data stays inside the client's walls. That is why every integration declares its tier.
| Sovereign-readyEverything runs in the client's network | ConnectedCalls your external service | |
|---|---|---|
| Where it runs | On the client's servers and GPUs | Partly on your cloud |
| Does data leave? | No | Yes, to your service |
| Air-gapped installs | Supported | Not supported |
| Activation | Like any node | Only with administrator approval |
| In the marketplace | Featured, Sovereign-ready badge | Labelled "calls an external service" |
Coming soon: the Sovereign-ready badge, the marketplace label and administrator approval. Today the author declares the tier and the team checks it.
From code to marketplace
How to become a provider.
- 01
Build
Coming soonDevelop your node, service or template following the provider guide.
- 02
Verify
AvailableThe team checks security, licences and the declared tier, and gives you the "Fornitore verificato" role.
- 03
Publish
AvailableYour integration appears in Emblema's marketplace, with your own publisher page.
- 04
Grow
Coming soonCo-marketing, introductions to FDEs and direct roadmap feedback.
What you get
Why integrate with Emblema.
- Available
A marketplace storefront
A publisher page and your integrations in front of the businesses that use Emblema.
- Available
FDEs as a channel
The people building client projects discover and use your services.
- Available
A say in the roadmap
In the providers-only lounge you talk directly to the product team.
- Coming soon
Provider guide and SDK
Public documentation for building nodes and services.
- Coming soon
Partner program
Co-marketing, joint events and introductions to clients.
- Coming soon
Trust from regulated industries
The Sovereign-ready badge tells clients their data stays in-house.
Provider program
Let's talk about your integration.
Join Discord and introduce yourself in #presentazioni with the "Richiesta verifica" tag. We will let you know when the provider guide is out.