How Simon works

You don’t need any of this to use Simon — but people often want to know what’s happening behind the curtain. Here it is in plain language.

The one-sentence version

Your Simon runs on a private cloud node that PrismScape sets up and manages; you reach it through a PrismScape front door (the web app or a chat channel), and PrismScape sits in the middle so your experience stays updated and can be customized — without you ever touching a server.

The three parts

1. Your private Simon (the node)

Every customer gets their own Simon, running on its own private cloud instance that PrismScape provisions and manages. It’s not a shared chatbot — it’s your agent, with your memory. That node quietly reaches out to PrismScape; nothing on the internet can reach in to it.

2. The middle (PrismScape)

When you send a message, it goes to PrismScape first. PrismScape checks it’s you, connects you to your Simon (and only yours), passes the message along, and brings the reply back. Because everything flows through this middle layer, PrismScape can improve the experience and tailor it for you without you reinstalling or reconfiguring anything.

3. The front door (you)

What you actually touch: the web app or a chat channel. Simple, familiar surfaces. All the complexity lives behind them.

Why it’s built this way

• So you never become a cloud administrator. The whole point is that a powerful agent shows up as an app or a contact — not as a server you have to operate.
• So it’s private and safe. Your Simon is yours alone, and its node doesn’t expose anything to the open internet — it only dials out to PrismScape.
• So it keeps getting better. Updates and customizations reach you through the middle layer automatically.

For the technically curious

Under the hood, your node runs an open agent runtime with a small connector that maintains a secure outbound connection to PrismScape; your agent’s control interface stays bound to the node itself and is never exposed publicly. You don’t need to think about any of that — but if you’re an engineer, that’s the shape of it.

What Simon is not

• It’s not a server you manage.
• It’s not a shared, one-size-fits-all bot.
• It’s not something you configure — it arrives trained and ready.

Next

→ Getting started if you haven’t said hello yet. → Using Simon from an agent to let your own AI assistant work with Simon.