For teams and companies
Ship your own AI setup to the people who should have it
A company marketplace is your own private shop of roles, kept wherever you keep your code. Someone installs a role and everything it needs comes with it: its skills, its helpers, its routines, its boards, sample data, and apps already connected. Who gets it, and how much they are allowed to see, is a separate decision.
What travels in a bundle
The unit is the role, not the file. Everything below is nested under the persona that needs it, so installing one thing gets a working environment rather than a checklist.
Personas
The role itself: its prompt, its voice, and which parts of the app it shows.
Skills
Standing knowledge as markdown. The difference between guessing at your product and quoting it.
Sub-agents
Specialists the persona hands work to.
Workflows
Scheduled, polled or triggered jobs. They arrive switched off.
Dashboards
Boards that arrive seeded rather than empty.
Datasets
Sample data in your real export format, so a swap for the real file just works.
Connectors
Pre-configured, with the secret sealed rather than pasted.
Hooks
Lifecycle automation that activates with the persona.
Three ways to deliver it
Same bundle, three ways of handing it over. The only difference is who fetches it and where the access key sits. That is the whole of it.
| Self-serve | Managed | Protected | |
|---|---|---|---|
| Who fetches it | the person installing | the app on their machine | the server, on its own |
| Where the access key lives | They paste in their own access key. | The server sends it sealed. The app opens it in memory for one fetch and forgets it. | Never leaves the server. No laptop ever sees it. |
| How content is sealed | Readable, or sealed with the app key when the author asks for it. | Sealed with a shared key compiled into the app. | A random key per marketplace, itself wrapped under a key that exists only on the server. |
| What it is for | An open bundle, or a small team who all have access to the source anyway. | Company content that is not secret, delivered without asking anyone to configure anything. | Anything you would not want copied out of the company. |
Connectors that arrive working, without handing out the key
Sealed
A shared sign-in is kept inside a sealed envelope, never written out as readable text. Changing it means sealing the new one the same way and swapping the envelope. Nobody ever pastes a bare key into a file.
Scoped per person
The bundle leaves a blank where the person goes, and Plexon fills it in with whoever is signed in. One bundle, and each person reaches only their own data. This is what makes a customer-facing bundle possible at all.
Narrowed
A bundle can hold back single actions from a service it otherwise opens up, so handing over a connection is not the same as handing over everything behind it.
A public page and a private one, from the same file
The same file that describes the bundle also carries the copy for a landing page. Mark it public and it becomes a real page on this site, findable in search. Mark it internal and name the group allowed to read it, and the page only loads after the server has checked that the person asking is still in that group. It is never built into the site, never indexed, and never linked from the public one.
Same page, same code, same shape. Only where the data comes from is different.
Run it yourselves, from your own admin panel
A company does not have to go through Plexon for the everyday work. Name one or more of your people as company admins and they sign in on this site and land on a panel that covers your company and nothing else: the people, their groups, the bundles, and the websites they published.
People and seats
Create an account, reset a password, disable someone who left, put a new hire in the right group, and end a seat at the end of its paid period. Prices and plans stay where they are.
Bundles from a zip
Zip the folder, upload it, and Plexon creates a private repository in your own GitHub organization and publishes the version. Every later version is another zip with a higher version number. Bring your own repository instead if you prefer.
Websites
See every site your members published, take one down, delete its repository, and decide who may publish at all. Nothing on the panel reaches another company.
What this does not do
Protected delivery keeps the access key off every laptop, stops people who should not have it, cuts off someone you have removed within about fifteen minutes, leaves no readable copy on disk, and makes a copied application folder useless on another machine.
It does not stop a currently entitled person, on hardware they control, from getting at content their own session is allowed to decrypt. No client-side scheme does. If something must stay unknown even to the people using it, it cannot travel in the bundle at all: it has to be issued per person, or held server-side and never sent.
We would rather write that down than let you find it out later.
Case study
An assistant for your customers
What a customer-facing bundle contains, and why almost nothing in it sends on its own.
Case study
An assistant for your team
The same machinery pointed inward, and the three things that change when it is.
Want one built for your company?
Talk to us