What should Ophraxx help with?

Ophraxx AI Discord Bot is now in beta

What's next: Ophraxx Lite • OX-B12 and OX-U45

Five personality modes now available for server admins

Building Ophraxx AI's multi-layer safety stack

A look at the real safety architecture powering Ophraxx AI — from LLM-based input screening and nine-category threat detection to automated fact-checking, PII redaction, and the philosophy behind requiring explanatory refusals.

From Discord message to AI reply: inside the Ophraxx pipeline

A detailed walkthrough of everything that happens between a user sending a message in Discord and receiving an Ophraxx AI reply — spanning spam detection, rate limiting, model routing, live tool calls, conversation memory, and chunked output delivery.

Ophraxx Lite: how we built our model lineup and routing system

An inside look at the three-model Ophraxx Lite lineup — what each model is designed for, how the prompt classifier automatically routes queries between them, how the five personality modes work, and what's coming next.

Admin controls: how server owners deploy and manage Ophraxx AI

A complete walkthrough of the Ophraxx AI admin experience — the interactive /setup command, guild configuration stored on our backend, usage tracking with per-user and per-guild limits, spam protection with automatic Discord timeouts, and the mod log integration that keeps server staff informed.

Designing the S1–S9 threat model: how we categorized safety risks

A research note on the decisions behind Ophraxx AI's nine-category threat model — why each category exists, how the safe-topic allowlist prevents over-refusal, and the reasoning behind the S8 and S9 categories that cover jailbreaks and persona abuse.

Routing complexity without asking: how the prompt classifier works

A research note on the design of Ophraxx AI's prompt classifier — the scoring system that automatically routes every query to the right model tier without requiring users to choose, and the tradeoffs behind the thresholds we selected.

Session memory design: why we chose 15 minutes and 20 messages

A research note on the design of Ophraxx AI's conversation session system — the tradeoffs behind the 15-minute session timeout and 20-message history cap, and why sessions are stored in memory rather than persisted to a database.