Sean7172331Q: Question About Pre-Publishing Code Scans and Tier 1 Site Limits
Hi, I have a quick question. As a vibe-coder, I currently use Claude Code and Google AI Studio to build websites, then import the completed NPM files into my hosting environment. I don’t currently use GitHub, though I may consider it later.
Since I already have the website code available, can I use your tool to scan my existing code before publishing? If so, should I copy and paste the code, or can I upload a ZIP file with all project files?
I also noticed Tier 1 includes 15 Fast Scans per month and 10 sites. Could you clarify what those limits mean in practice?
Lastly, if I add a site, can I remove or replace it later? Some projects fail while others take off, so I may need to rotate sites over time.
Rome_Rafter
Jun 1, 2026A: Great questions! I'd love to convince you to use Github. It will make it effortless for your agents to send copies of the code back and forth between the AI studio and local, and Google and Claude both understand how to use it. Plus, you'll never have to worry about keeping it in sync again. Feel free to send me an email ([email protected]) and we can set up a call—happy to demo it for you.
Currently Github is the only way to get code to the Rafter Security Engine, but the Rafter CLI has a lot of great features locally. It's free and open source, so you can grab the prompt on rafter.so and drop it into your agents, that'll get it set up.
What are Scans? Fast Scans can fit into your workflow in a handful of ways. The simplest is to go to rafter.so/dashboard and analyze a codebase. Then you can copy-paste prompt-engineered vulnerability reports into your coding agents. I recommend this after any substantial change or whenever you touch key subsystems (authentication, payments, etc). Alternatively, you can use the Rafter CLI to give your agents the ability to scan on your behalf, as they develop the features, so you don't have to even think about it. Dropping in the prompt or following the walkthrough on rafter.so/dashboard can walk you through the setup. So if you're shipping features every other day on one codebase 15 Fast scans makes sense.
As for Sites, the analysis is a combination of site speed, security, accessibility, and other best practices. We've found 10 to be a good balance for most users, who do a lot more rescanning rather than adding new sites. So we cap total Sites (with no way to delete) and provide very generous rescans (if it ever gets in your way, just send me an email and I'll bump limits). Earlier today per some other AppSumo feedback, we did just ship a way to archive sites so it's easy to keep track. They still count toward the limit.
But if you'd like to advocate for usage-based Sites, please make the case—we want to give you what you want!
Thanks for your thoughtful response. I’ll take you up on your offer and email you to set up some time for a demo.
Yes, you know I’m a bit behind when it comes to GitHub in general, and I know it makes the most sense, so I’m going to look further into it. I’ll set aside some time and reach out via email. Maybe we can do a demo together, and I can ask questions from there.
Thank you!
Verified purchaser
We definitely can, I'd love to help you get set up.
to confirm on tier one for example you say "So we cap total Sites (with no way to delete)" does that mean we can never delete sites to make space for others and when we hit our cap thats it cant do anything else??
Verified purchaser
That's the way we have it structured—rather than limiting how often you can scan, we limit total sites. Because many AppSumo users are agencies or manage large portfolios, that's part of the reason we offer a more generous rate than our regular subscriptions: 10, 100, and unlimited. You can email me ([email protected]) to delete some if you hit your limit. Would you prefer a different structure?
I would prefer the ability to delete sites I dont need or use once I hit 10 sites in the app instead of having to email everytime to delete. Other tools unrelated when they set a site cap they allow us to delete sites to make space for others. Visby ai is an example. If you had such a feature id likely buy.