A layer in your stack. Not another system.

One composable layer on the systems you already operate serves every audience: people, AI and your own applications. One integration instead of one tool per audience.

Build on what you have

Every audience tool you run is one more integration, one more identity setup, one more security review and one more vendor. Smint.io is one layer on the systems you already operate, and every audience gets its experience from it: portals for people, Sminted AI for assistants and agents, the API for your own applications.

Build on what you have

Your DAM, PIM, ECM or CMS stays the system of record. A connector links it to the Unified Semantic Context Layer, near real-time: push where your system supports it, pull where it doesn't. Nothing is re-uploaded.

One integration, every audience

One data basis serves portals for people, Sminted AI for assistants and agents, and the API for your own applications and downstream systems. One integration instead of one per audience tool.

Enterprise-grade

SOC 2 Type II, audited annually since 2023. SSO via SAML or OIDC with SCIM provisioning. Audit trails for human and agent access. Self-hosting on AWS or Azure; hosting region your choice, including the EU.

Index, metadata and previews only

By default the platform holds the search index, the asset metadata and preview files. Originals stay in your systems and are fetched on demand, or we host them where you want that. No new silo.

With Sminted AI, AI access always happens under your rules

Every portal exposes a standard MCP server: one endpoint, any MCP client, no plugin per tool. An assistant or agent reads through it with the permissions of that specific portal user and nothing more, and every agent access is in the audit trail beside the human ones. Your own applications take the same content through the API, as some customers do to supply their partners. One data basis, three surfaces, one permission model.

How Sminted AI works

Where the layer sits

Your systems above, Smint.io in between, your audiences below.

Your existing systems

  • DAM
  • PIM
  • ECM / SharePoint
  • CMS
  • MRM
  • Custom systems

People

  • Partners
  • Press
  • Markets
  • Internal teams

AI

  • Assistants
  • Agents

Applications

  • Your own apps
  • Downstream systems
Custom development & SDKs

In use at

LEICHTKitchens

The Agravity connector was built for its brand portal and is now a standard connector; one portal for more than 1,000 partners in 55+ countries.

Global printing services companyAnonymized

Client portals operated in the provider's own VPC on AWS under strict isolation requirements.

ArperFurniture design

Thron DAM and PIM on one foundation; an agency built the UI components with the SDKs.

Working with Smint.io enables our customers to quickly and easily publish assets in a customized user experience. The simplicity and the wide range of customization options are convincing with every further project.
Philip AxmannDirector of Global Business Development, Picturepark – a FotoWare Company

Questions IT teams ask

By default: the search index, the asset metadata and preview files. Originals stay in your source systems and are fetched on demand. If you prefer, we host the originals as well. You can choose the hosting region, EU included, or run the platform in your own AWS or Azure account.

SSO via SAML or OIDC with your identity provider, and SCIM for automated user provisioning. Local user management where SSO isn't wanted. External audiences come in by invitation or register with their company email.

Don't worry, the portals stay up. Audience traffic is answered from the platform's own index. Only original downloads need your systems, and we can host those originals too if you want. A source can be changed later without touching the experiences on top. IHG replaced SharePoint with Censhare underneath a running portal.

Yes. The documentation portal at https://documentation.smint.io is public, with no account needed, and it has its own MCP server. It covers the platform API, the portal MCP server and the component SDKs.

Your content never left your systems in the first place. What the platform holds (e.g. index, metadata, previews and uploads) can be exported on request.

Agents see exactly what the portal user they act for may see. Every portal has a standard MCP server, and it applies that user's exact permissions. Agent access appears in the audit trail like human access.

Bring your stack diagram