Your agent can now build software on Plexara and release it: an application with its own database, or a website on your own domain, with a person deciding what goes live. This month we moved plexara.io onto it.
Plexara is built in layers, and each layer is pressure-tested before the next one is built on it. Applications are made of automations, and automations hold the agent to the practices of a disciplined software team: drafts it can run without changing anything, tests that must pass before a save, releases, and rollback. Each capability reaches agents first, and the portal screens follow. Work runs from a person to their agent to Plexara: you say what you need, the agent builds it with Plexara's tools, and people review, approve, and use the result in the portal.
Because every capability is a tool an agent calls, a new frontier model receives all of it the day it connects. Anthropic's newest models are already at work on Plexara deployments, over the same open protocols as the models before them. Claude, ChatGPT, Gemini, and the ones that replace them get governed access to your data, the knowledge your team has recorded, and every tool below. The chatbot built into each vendor's product works on that one system, with that vendor's model.
plexara.io now runs on Plexara
On November 13, plexara.io moved onto Plexara Sites on our own deployment. Its pages, lessons, Insights, newsletter archive, and more than 2,000 images are served by the same platform our clients use. The contact form is a Plexara form, and the facility map draws its tiles from our deployment. The site's layouts and navigation are templates the platform renders, so an edit made on the platform holds.
We run it under the same rules:
Agents work in dev. This month's lessons and Insights, and this issue's archive page, were written into dev by an agent and reviewed at a private address behind our sign-in.
People promote. Production requires approval, and since this week's release the platform holds every agent at dev. These pages reached plexara.io when one of us promoted them.
The rules live on the deployment. What our copy may say, and the checks to run before a promote, are a knowledge page on our deployment, and the site points every agent to it.
Deasil's other sites moved this month too. A marketing site, intranet, or partner portal that sits where your data and your agent cannot reach moves the same way: from its source, one environment at a time, with a person deciding what goes live.