What is Gunnie.ai, in plain words?
An AI delivery team that works inside the systems you already use. Today it reviews code and answers questions from your web shop, product data, tickets and code; in the beta it also prepares, estimates and builds tickets. Your people check and approve the work. Gunnie.ai decides what the AI may reach and writes down every step.
What problem does it solve?
Developers lose a large part of their week to groundwork: reading tickets, collecting context, estimating, reviewing, writing release notes. AI can do much of that, but most companies hesitate to give it access to their shop, tickets and code, because nobody can see what it touches. Gunnie.ai does the groundwork and keeps the AI inside your rules, so your team spends its time on decisions.
Who is it for?
Companies with a development team, in house or hired, that work from tickets and pull requests. Developers get the reviews and the groundwork; product owners, support and sales can ask plain questions about products, orders and tickets without needing a developer.
How quickly can we start?
Asking questions and starting code reviews works as soon as your systems are connected. An admin connects each system once with an access token, and every member adds one address to their AI assistant. The routines that run on their own, such as pre-refinement and estimates, start in the beta: we set them up with you and tune the skills to how your team works.
Do we have to change our tools or the way we work?
No. Gunnie.ai works with your Jira or Linear, Confluence, Bitbucket, GitHub or GitLab, Magento, Akeneo and Figma as they are, and the routines follow your process, your definition of done and the standards in your repositories.
Which AI assistants does it work with?
Claude, ChatGPT and other assistants that support MCP, the open standard for connectors. Your team keeps the assistant it already uses.
Does it work with Slack?
It will, with the beta. Install the Gunnie.ai Slack app and pick a channel: the routines report there, so your team sees what the AI did without opening another tool. Answer in the thread, with a reply or a ✅, and the AI gets to work within the reach of the person who replied. The app comes to the Slack Marketplace later.
Will it replace our developers?
No. It takes the groundwork off their plate. People still decide what gets built, approve every change and decide what ships.
Can the AI change things in our systems?
Only what you allow. Each role gets its own tools, and allow-lists limit which projects, repositories and files are within reach. Most tools only read. Anything that changes something, like creating a ticket or a note a routine wants to add, waits until it is approved in Gunnie.ai, whatever AI assistant was used. Files that hold secrets, such as .env files and keys, are never read. The code review never posts on a pull request by itself.
Is our data safe?
Gunnie.ai reads your systems live and keeps no copy of your products, tickets or code; only a routine’s result and a change waiting for approval are kept, for 30 days. The call log records who did what and when, never the question or the answer. Files that hold secrets are never read. Access tokens are stored encrypted, the server runs in a European data centre, and nothing is used to train AI models.
Which AI runs the code review and the routines?
Claude, through Gunnie’s own account, in the EU. Usage is counted per organisation, within a monthly budget you set, and under Anthropic’s commercial terms your data is not used to train models.
What does it cost?
During the beta we agree the price with each participating company. Code reviews and routine runs show their cost one by one, within a monthly budget you set yourself, and every routine has a budget of its own.