Bot Pages
Turn prompts into authenticated apps.
A bot can turn its work into an authenticated internal app, then Botyard hosts it behind auth, policy, monitoring, and audit.
Prompt to App Pipeline
From request to governed app link.
Bot Pages make the full journey visible: prompt, build, service logs, registration, OAuth2 policy gate, shareable Bot Page link, demo app preview, and audit trail.
Ask for an internal app
A teammate asks a bot for a dashboard, review tool, report viewer, or one-off operational workflow.
Code, service, logs
The bot builds the web app, starts a local service, and streams progress through Botyard.
Service registered
Botyard keeps the service reachable, monitored, and tied to the bot that created it.
OAuth2 and policy
Requests pass through Botyard auth, app policy, org access rules, and user-level checks before the app loads.
Bot Page link
The bot returns a durable internal URL your team can open without exposing the service to the public internet.
Preview and trail
Every authenticated visit is tied back to the user, bot, app policy, and workspace audit trail.
Why it matters
Internal app hosting without the internal platform tax.
Teams already ask bots to produce dashboards, data cleanups, and decision tools. The hard part is not making a Streamlit prototype. The hard part is getting it off a laptop, behind corporate identity, monitored, governed, and safely shared with the right people.
Bot Pages close that gap. Bots can expose local web apps, keep persistent services running, support WebSocket-backed experiences, and publish multiple previews while Botyard handles access control and audit.
OAuth2-protected app access
App-defined policy engine
Default bot, org, and user permissions
Service monitoring and logs
Persistent background services
WebSocket proxy support
Streamlit and internal tool support
Multiple previews per bot
File and report previews when bots build them
Authenticated-user audit trail
Custom domain requirements can be scoped through enterprise onboarding
Not a presigned link
A Bot Page is an app surface, not a file handoff.
Presigned links are useful for temporary files. Bot Pages are for live, authenticated internal apps that need identity, policy, monitoring, and user-level accountability.
A presigned link
- Usually grants access to one object or temporary file.
- Hard to express org policy beyond link expiry.
- Poor fit for interactive apps, sockets, background jobs, or user-level audit.
A Bot Page
- Hosts the app experience behind Botyard identity.
- Applies OAuth2, app policy, org access, and user permissions before each session.
- Supports live internal apps with logs, monitoring, previews, and audit trails.
Build the app, keep the controls
Give every bot a safe place to publish useful software.
Bot Pages let teams move from prompt to internal app without bypassing OAuth2, app policy, access control, monitoring, or audit expectations.
Get Started