roadmap
Where Imposters is heading. Each item links to an issue: comment there with your use case, or add a 馃憤 to the ones you need most. Priorities shift with that feedback.
What is already shipped is in the README. Maintenance work and internal notes live in DEVELOPMENT.md.
now3 items
Website and docs
a landing page with an in-browser playground, a getting-started guide, reference docs for every feature, and this roadmap
Monitoring UI
a live dashboard across all imposters (which are up, traffic, errors and latency), and a live view inside each one (requests as they arrive, stub hit counts, requests no stub matched)
AI-friendly
an
imposters mcpserver, so coding agents can create imposters, add stubs and read captured requests as tools, plusllms.txtand agent-oriented docs
next5 items
OpenAPI import
generate an imposter and its stubs from an OpenAPI 3.x spec
Mountebank adapter
accept Mountebank imposter JSON, a direct migration path for Mountebank users
Record and replay
binary stub bodies, then export recorded proxy traffic as a config file and re-import it
S3 completeness
list pagination and
delimiter, bucket settings that read back,aws-chunkeduploads, and keys with.or..segmentsA service graph
callbacks have shipped (stubs that call other services before answering or after, see the README); next, the calls on the stub cards and the request page, then a live graph of who calls whom in the web UI
later4 items
WebSocket mocking
scripted message sequences, replies and dropped connections on cue
gRPC and raw TCP
further protocols as imposter extensions
More cloud emulators
in-memory services in the S3 extension's mould, starting with SQS
Hosted Imposters (exploring)
shared mock environments for a team or CI, with nothing to run locally
Suggest something or follow along in the issues 路 ROADMAP.md