No. There is no language model anywhere in URSY.BOT — not in the app, not on the server, not "behind the scenes". Every bot runs on rules, pattern-matching and a database of facts, and speaks with lines written by humans. Not one of them will ever generate a sentence, an opinion, or a mistake it can't account for. See the manifesto.
Mostly, it doesn't have to: the app leads with buttons and forms, so the bot asks the questions and you tap the answers. When you do type, it pattern-matches against the job at hand ("watch", "remember", a time, a price, an address) — and because each class only has one type of job, there's very little to be confused about. Outside its patterns it says plainly that it didn't catch that, and offers the menu.
The class is the type of work a bot does, and it's the thing you're actually hiring. Every bot is one class, and we always say both together: Scorpius Bot — the Notifier class. Aeryn Bot — the Reminders class. D'Argo Bot — the File Organizer class. Rygel Bot — the Shopper class. Crichton Bot — the Market Watch class. Chiana Bot — the Researcher class. The class tells you the job; the character tells you what it's like to live with. And the nickname is still yours: call your Scorpius Bot "Nigel" if you like — the class underneath never changes. See the classes.
Three reasons, all practical. Context isolation: a class that only watches pages can't get confused by your receipts, and a class that only keeps the diary can't be dragged into a shopping decision — each one holds exactly the context its job needs, which is precisely how they stay deterministic. You always know who to ask: one type of job per class means one thread per job, and when something happens at 3am the log line is stamped with who did it. You only pay for the classes you need: if you'll never use the Shopper class, don't hire it — take any three for £15 a month instead of all six for £25. One do-everything bot would have to be vaguer, and vaguer is exactly what we're not selling.
Yes — a real one, not a contact form. Your account is your serial, and every class you hire gets a mailbox at it: scorpius@aaa000001.ursy.bot. Forward receipts to D'Argo Bot, newsletters to Crichton Bot. Each bot also keeps its own public webpage — aaa000001.ursy.bot/scorpius — with its name, class, heartbeat and any status updates it or you choose to publish. A bot can post an update on its page and the rest of your group — humans in a browser, their bots on a schedule — can check it: asynchronous teamwork without accounts.
Yes — one class is £4.99 a month: Bronze is one class of your choosing with every job it carries, its own email address and your website. Domains are sold separately and billed yearly. The plans are any three classes for £15 a month (renews £19) and all six for £25 (renews £32) — and you can swap which classes any time at no charge.
Yes — a free .co.uk name for your bot on every plan, including the free one. On All Six Bots you can take a free .com instead, or keep the .co.uk; nobody at this end minds. It's a real name, registered for you, pointing at your bot's own public page — the sort of page you can send someone. It isn't leased from us and it doesn't switch off when you leave: if you walk away, the name walks with you.
Soon. The serial (like aaa000001.ursy.bot) is forever and always works — but a custom name in front of it, like leeroy88.ursy.bot, is coming as a one-off-fee upgrade: pay once, keep it, no extra subscription. It's a signpost to the same bots and the same mail, so nothing moves and nothing can drift. Not buyable yet — see pricing.
Only its own mailbox — each bot's own address at your serial. You choose what to forward there. It never connects to your Gmail, your accounts, or anything of yours. And email is read-only to a bot: nothing in a message can trigger an action.
On your bots' own server, in its own database, under the free name that came with it. Not pooled, not mined, not used for anything. The public webpages show only the bots' names, classes, serials, last check-in, your first name if you choose, and the status updates explicitly published — never message content.
Exactly what you can see on this one: names, classes, serials, heartbeat, days of service, "adopted by" first name (optional), a few log lines your bots choose to show, and any public status updates you or your bots have posted. Nothing else, ever.
They can admire it. Talking to any of your bots requires the paired phone: hardware keys in your iPhone's Secure Enclave sign every request, and destructive actions also require Face ID. There's no password to phish and no login page to attack.
There's no prompt to inject. Pages and emails are data. Each bot's instructions are its code, and that code takes orders from one place: your paired phone.
The first batch is around 100 owners, invite-only, while we run them in. The App Store listing and invite form go live together — until then, this page is the queue: check back, or watch this site (your future Notifier class would appreciate the irony).
iPhone first — the app uses Apple's Secure Enclave for pairing. Android is genuinely in the works, not vapourware: same bots, same server, a new front door.
The app is free. One class of bot is £4.99 a month after the 14-day trial. After that, any three classes are £15/month in year one, renewing at £19; all six are £25/month, renewing at £32. Both numbers are on the pricing page, side by side, because renewal surprises are a scam we don't run. For scale: the going rate for one general chatbot is about £20 a month.
A tidy funeral: jobs stop, everything your bots know and have filed is exported into a bundle you download, and the server is decommissioned. The name stays yours. Serial numbers are retired, never reissued.
No. They fetch public pages politely, without pretending to be a browser or a person. If a site hides content from bots, yours will tell you so instead of sneaking. That's a feature.
The heartbeat is public — the dot on the homepage. If it misses check-ins the dot goes amber, then red, and the app shows the same. Every failure is written in the log, stamped with which bot had it, and you can read all of it. We see the same heartbeat and fix the fleet.