Your brand on the app. Your secrets stay yours.

Build a gold-standard persona for each role (Engineer, Designer, Analyst) and publish it to your company once. Every employee signs in and gets the same one: the same system prompt, the same agents, skills, and tools, the same defaults. No setup, no drift between machines.

• Every employee gets the same setup on sign-in: the same instructions, the same agents, skills, and tools already switched on.
• Make the persona’s instructions a secret item. Your people use it, they cannot read or copy it.
• Arrives through your managed company setup, and which of your plans carries it is your call. A Pro-level plan can bring a persona for the role; company and org-level personas need one of your plans that grants Premium.

Two things your team does together, on infrastructure you own. A shared project board is one board everyone works off, and a published website is a real page on the internet. Both live in a GitHub organization your company controls, and neither asks the person using it to have a GitHub account, a token, or permission to create a repository.

• An administrator connects one repository for the whole company. Adding a board after that is a name and a button, for anyone.
• Boards are found, not registered: create one and your team sees it on their next sync, with the name you gave it.
• Sync is a button. Everyone’s edits merge; a real clash names the record and stops rather than pushing a file full of conflict markers.
• Each person gets a short-lived push credential from your company, never a token to paste. Remove them from the team and the next one is refused.
• The same goes for websites: your company owns the repository and the address, and can disconnect Plexon from its own GitHub settings whenever it likes.

Not every company pays list price. We can set a custom plan for yours at a price we agree on, built around your own personas and flows. It appears on your company page in Plexon like a normal plan, with a link you can share with whoever needs to buy.

You are not limited to one. Most companies run a lower-priced plan to get people in, with its own persona and website publishing, alongside a fuller plan for the roles that need secret content and the heavier models. Each plan carries whichever bundle you point it at.

• Buying assigns the person to your company. They get your personas, flows, branding, and seats from the first sign-in.
• Each plan grants Pro or Premium features at the price you set.
• Start people on a Pro-level plan that still carries your own persona and lets them publish websites, then move the ones who need more onto a Premium plan.
• Run more than one plan at once: one for your team, one for your clients, each with its own bundle.
• Signed-in people check out on the page. Anyone else uses the shared link and activates with the email they paid with.
• Anyone on your team can pay for a colleague. Type their work email and the plan is waiting the first time they sign in, account or not.

Package your best work as secret items. Your clients install them and use them like anything else. They cannot open the system prompt, read the knowledge base, or copy the files to hand to someone else. This is how a company shares its know-how without giving it away.

Secret items cover agents, personas, and skills.

Your team opens Plexon and sees your name. The splash screen, the window title, and the header carry your company branding in place of ours.

• Name and tagline apply on their own once we set up your company.
• Custom theming (logo, colors, deeper UI branding) is available for white-label partners. Tell us what you need.
• No build, no servers to run. It ships through the official, signed Plexon app.

A new hire signs in and your setup is already there. No checklist, no manual install. Hand someone a laptop, have them sign in, and they are working with your AI the same minute.

Pre-loaded and pre-activated. The items you mark as active turn on by themselves.

You keep one curated set of content. Push a change and it lands on every machine the next time the app opens. You curate. Plexon delivers.

• Your company content stays locked in place. People cannot remove it by accident.
• Updates are quiet. Open the app and the latest version is already in place.

When someone on your team signs in, Plexon can prove to your own backend that they belong to your company, and which group they are in. No call back to us at request time.

• Every request to your own systems carries a signed pass saying which company it came from. Your side checks it with a key only you hold.
• Which group the person belongs to travels with it, so your systems can decide what each role reaches.
• Secrets you bundle in, like the keys to your own services, stay encrypted and are opened only in memory while a request runs. They never sit on anyone else’s machine in plain text.

Keep the app focused on what your people actually use. Hide or lock features per company or per group.

• Hard-lock a panel and it disappears for that group. Or hide it by default and let people turn it on themselves.
• Sort users into groups and give each group its own content and its own visible features.
• Mark items active and they switch on by themselves. Your people start working, not configuring.

The questions your team asks about your own product have their answers in your private codebase. Plexon lets a role answer from that code without the code ever reaching a laptop: your CI ships a graph of it, scanned clean, into your company bundle.

• Your own CI builds a graph of the codebase on every push to production and development: which function computes a value, which table and column it reads, what a product feature is called in code.
• The graph ships inside your company bundle. Not one source file does: every byte of the graph is scanned for credentials and personal data before it leaves your CI, and a hit stops the push.
• The role that needs it answers "which table does the algorithm read" from the code, cites the file and line, and follows your production or development branch with one switch.
• No other assistant we know of ships a company its own codebase this way: answered from, never handed over.

How it works, for your engineers: the marketplace page.

• Everything stored, every secret and every sign-in is encrypted.
• A server that keeps nothing between one request and the next.
• Sign-in details are never written to anyone’s machine in plain text.

What you run, once you have a company

A company on Plexon gets its own panel inside the app everyone already installed. These four pages cover what is in it.

• Company admin panel. Approve people, put them in groups, see who holds a seat, and decide which catalogs and buttons each group gets.
• Company marketplaces. Your own catalog of skills, agents, personas and workflows. Plexon holds the repository, or you point at one you own.
• Company websites. Every site your people published, on your domain, with the switch that decides who is allowed to publish at all.
• Persona agreements. A role that reaches sensitive data can require a written agreement first, recorded against the exact text shown.