Scriptus vs Botpress
Botpress is a capable agent platform: Studio, conversations as the meter, webchat and WhatsApp, a free tier. Scriptus was never trying to be that studio. If you need a construction environment for support, lead-gen, or product agents, Botpress is the better product. If you have a book or methodology and want it working as a branded, cited, monetized embed, you do not need that studio. You need the product.
Last researched: 4 September 2026. Botpress prices below are from botpress.com/pricing that day. Scriptus prices are from getscriptus.com.
You want one purpose-built knowledge product: your material, your brand, citations, entitlements, durable history, and reader billing — without staffing a bot studio. You would rather pay for a finished engagement than operate conversations, seats, and storage add-ons.
You are a product, CX, or developer team designing agents. You want a visual studio, WhatsApp, a free 100-conversation start, and conversation-based pricing you can model. You will operate the agent after you build it.
| Decision | Scriptus | Botpress |
|---|---|---|
| Job the software is for | One knowledge product from your book or methodology | Design and run customer-support and other agents |
| Who operates it after launch | Scriptus maintains the platform; you own the offer and the IP | Your team owns the studio, conversation packs, and integrations |
| Identity and history | Owner-side identity, entitlements, and durable conversation history are part of the product | You build the rest of the product around Botpress sessions and tables |
| Reader paywall | 3-question trial or free access; checkout on your Woo, Kajabi, Stripe, or Whop | You assemble billing and access control on top of the kit |
| Citations and refusal | Answers from your pages, or it says it does not know. We will demo a refusal. | You design grounding and guardrails. Possible, not the default offer. |
| Studio / canvas | Not the product. You do not draw branches to go live. | Botpress Studio is the point. This is why builder teams buy it. |
| Channels | Site embed first. Optional in-chat voice. Not an IVR platform. | Webchat, WhatsApp on paid plans, voice on Enterprise — from their pricing page. |
| What you pay | $5,000 setup + $500/month. No conversation pack for the operator engagement. No revenue share. | Free: $0 / 100 conversations. Plus: $150/month billed annually, 250 conversations/month, extra packs $65/100. Team and Enterprise sit above that with higher or custom volume. From botpress.com/pricing, 4 September 2026. |
A real free tier. Conversation pricing instead of per-seat. Unlimited agents on paid plans. WhatsApp. A studio developers already know how to search. If that is your job, stay. Scriptus will not grow a studio to chase that buyer.
Purpose-built. Identity, entitlements, citations, and reader commerce are the product. You are not buying conversation packs. The first Scriptus programming lived on a general kit (Voiceflow); the rebuild happened so those layers could be owned. Botpress is a different excellent kit. Same structural gap if the job is a book as a product.
Plus at $150/month can look cheaper than Scriptus. It is a studio subscription plus conversation packs and AI-usage rules on that page. Scriptus’s $5,000 + $500 is the engagement that includes the product around the model.
Botpress also sells “Built and managed for you” on the same pricing page. That is their implementation offer. We will not guess its scoped price. Compare a scoped Botpress build to Scriptus only if both quotes are in front of you.
Last verified: 4 September 2026 · Sources: getscriptus.com, botpress.com/pricing
There is no import of a Botpress bot into Scriptus. We take your source material and build the tenant from that, not from your flows. Export transcripts you still need. Parallel run is possible until the new embed is signed off.
Choose Botpress if you are building agents as a practice. Choose Scriptus if you already have the knowledge and want the product without the practice. Choose Voiceflow, Vapi, or Retell if you specifically want a CX canvas or a phone runtime — still this family, not ours. If you only need anonymous Q&A over a PDF, use NotebookLM.
For authors who want a branded book bot without a studio, it can be. For teams buying an agent platform, Botpress is the category product.
Because you are buying different things. Botpress is a builder. Scriptus is a deployed knowledge product after a $5,000 build, with no share of reader revenue.
Often, yes — with enough studio work and a billing stack you own. That is the point. Scriptus is for people who do not want that project.
Same family: general kits. Voiceflow leans CX canvas. Vapi and Retell lean phone. Synthflow leans enterprise voice. The fit test is identical.