← All documentation
DOCS · OVERVIEW

Documentation

Plain-language guide to every surface, skill, and command in the platform.

What is it?

Mephit is a cybersecurity platform built around a chat interface. You ask a question or fire a slash command, a router activates the relevant specialist skills (recon, intel, RE, blue team, etc.), real lookups run in parallel against live data sources, and the result is synthesised into one answer.

It is built for pentesters, CTF players, red and blue team operators, and security researchers. There are no warnings, no disclaimers, no “I can’t help with that.” Scope is yours.

Building blocks

CHAT
The interactive console
Streaming chat with a slash-command picker, attachments, conversation history, and auto-titled threads. Read more →
PROJECTS
Per-engagement workspaces
Group chats, assets (servers, domains, IPs, apps, services), tech-stack tags, goals and notes. Read more →
SSH SERVERS
Bring your own boxes
Register SSH targets, propose and approve commands from chat, audit every run. Read more →
SKILLS
Router-driven specialists
15 skills, 24 slash commands. The router picks which specialists run each turn. Read more →

Design choices

Live lookups, not stale training data. Reputation, breach indices, certs, advisories, and sandbox results are queried at chat time. The model never invents a CVE or a WHOIS record.

Human-in-the-loop for execution. The model never runs commands on your boxes. It proposes; you click run. Every execution is audited and rate-limited.

Chat is just one surface. A CLI, IDE plugin, and autonomous agents are on the roadmap — they all share the same skills, projects, history, and registered servers.

No vendor lock-in on intel. Each provider is a replaceable adapter. We disclose the active provider list to enterprise customers on request and otherwise treat it as implementation detail.

Where to next

START HERE
Getting started
Sign up, send your first prompt, and learn the keyboard affordances. Open guide →
SECURITY
How your data is handled
Encryption at rest, audit logs, what we do (and don’t) send to upstream providers. Open guide →