Run · Deployment experiences
The same governed agent, wherever your team meets it.
Not every agent should look like a chat window. Augela separates what an agent knows and is governed by from where it actually shows up, so the same configuration can serve very different surfaces.
Why the surface shouldn't dictate the setup
A document agent and a chat agent can share everything except the window.
Building a chat bot and a document assistant as two unrelated products means duplicating guardrails, knowledge and persona between them, and hoping they never drift apart. Augela treats the experience as one setting on an otherwise identical agent.
The experiences available today
Four shapes, one governance model.
- Chat
- The conversational surface most people picture first, inside the console, or standalone.
- Document
- A workspace built around producing and editing a document, not a back-and-forth conversation.
- On your own website
- Embed the hosted chat, or build your own interface in your own design. No admin controls on show.
- Signal-driven
- An agent that watches Slack or an inbox and acts on what it finds, rather than waiting to be asked.
What the agent knows comes from Knowledge Hub and Connectors; what it's allowed to say is the same Governance Mode regardless of the surface.
Your chat on your own website
In your design, on the websites you choose.
- Hosted or your own
- Embed the chat as it is, or build your own interface and connect it to the agent.
- You pick the websites
- Choose in Augela which websites may use it. No technical setup needed on our side.
- Live example
- Renteden's "Zeptej se" chat answers visitors with live prices and availability.
See it at work: Renteden's website chat.
Built-in protection against misuse
A public chat with limits you set.
- Limits per visitor
- How many messages one visitor can send, and how many per day.
- A daily ceiling
- A cap for the whole chat each day, with an email to you when it is reached.
- Your own wording
- What a visitor sees at a limit is written by you, not a generic error.
- Invisible bot check
- Optional, using Cloudflare Turnstile. Visitors never have to give an email address.
FAQ
Teams choosing a deployment surface are asking
Can the same agent run as both a chat widget and a document experience?
An agent is configured for one experience type at a time. But nothing stops you standing up two agents, with the same profile and the same knowledge, for two different surfaces.
Can we embed an agent on our own website?
Yes, two ways. Embed the hosted chat, or build your own interface in your own design and connect it to the agent. You choose in Augela which websites may use it, and there is no technical setup needed on our side.
How is a public chat protected against misuse?
You set message limits per visitor and per day, and a daily ceiling for the whole chat that emails you when it is reached. The message a visitor sees at a limit is in your own words. An invisible bot check (Cloudflare Turnstile) can be switched on, and visitors never have to give an email address.
Does an embedded agent get the same governance as an internal one?
Yes, identically. Guardrails, watch words, company memory and audit logging all apply the same way. On your website, visitors get the confirmed answer without ever seeing who confirmed it.
One agent, configured once. Chat, document, or embedded on your own site.
Twenty minutes with the founder. No slides. The real product.
