Outline

This page outlines my mind set for future updates to Gambit and is more of a personal ramble than technical docs.

The future of Gambit

The initial roadmap outlines my goals for getting to a stable 1.0 release. These mostly focus on what I think are the bare minimum for a framework usable on real-world engagements. Granted, this outline is subject to change based off of user feedback and my own personal preferences.

Post 1.0

While I don't have the specifics planned out, once Gambit is in a stable state, I have some ideas for features I think other frameworks are lacking in both features and QOL. The goal of Gambit is to malleable and easy to customize, not be the next evasion-as-a-service tool. This means that not all updates will feature the newest groundbreaking ttp. A lot of them will be features useful to operators on real engagements or QOL updates that make people want to continue using Gambit (nobody wants to be frustrated with teamservers crashing or bad UI/UX).

User Input

User input and feedback will play a massive role in what features I add. I'm a one-man-show afterall. With that being said, please submit a feature request as an issue on Github, in Discord, or through any other means of contacting me.