Free tools
See what is wrong with your cloud, site and code. Free.
Five free tools from FreshField. No sign-up, no card. Bring your own site, code, log file or read-only cloud keys and get a clear list of what to fix, in plain words.
FreshField Save
Find money you are wasting in your cloud.
You give: Your AWS read-only keys
- Idle disks, unused IPs and forgotten servers
- Old snapshots, gp2 disks and older instance types
- A monthly figure for each fix, and how to do it
FreshField Visualize
See your cloud as a diagram, drawn for you.
You give: Your AWS read-only keys
- Regions, networks, subnets, servers, databases, buckets
- What the internet can reach, with risky paths in red
- Download as SVG or PNG for your docs
FreshField Observe
Free scan for security issues and bugs.
You give: Your website, your code, or your cloud keys
- Missing protections, exposed files and leaked keys
- Injection risks, unsafe settings and swallowed errors in code
- Open ports, public data and missing MFA in the cloud
FreshField Migrate
Ready to leave AWS? See what it takes and what it saves.
You give: Your AWS read-only keys
- A readiness score for Azure, Google Cloud or your own servers
- What each resource becomes, and what blocks it
- Monthly cost there, the saving, and the work in person-days
FreshField Log check
Your top 5 log problems in ten minutes.
You give: One log file (read in your browser)
- Emails, IPs, card numbers and keys masked first
- The five problems that matter most, with how often and when
- Why each one hurts, and how to fix it
Your keys, your site, your code. Only yours.
- Read-only. Use a user with only the AWS ViewOnlyAccess and SecurityAudit policies. We refuse root keys.
- Used once, never kept. Your keys go over HTTPS to our scanner for this scan only. They are not saved, not logged, and cleared from this page as soon as the scan ends.
- Only you see the results. Nothing is sent anywhere unless you ask us to email the report to you.
- Delete the key after. Or use temporary keys (ASIA...), which expire on their own.
- Websites: we scan a site only after you prove it is yours with a file, a meta tag or a DNS record.
- Code: scanned inside your browser. It is never uploaded.
- Logs: read inside your browser, with personal data masked first. Never uploaded.
Free tools vs FreshField
| Free | FreshField | |
|---|---|---|
| How often | One snapshot | All the time |
| What it sees | Settings and files | Your running app, live |
| Problems | A list to fix | Cause, evidence and the line of code |
| Fixes | You do them | Tested fix as a pull request |
| Diagram | From network layout | From real traffic |
About the free tools
FreshField’s free tools are five self-serve checks for your cloud, website, code and logs. Each one gives a clear list of what to fix, with no sign-up and no card.
- Pick a tool: Save, Visualize, Observe, Migrate or Log check.
- Bring your own read-only cloud keys, your website, your code or a log file.
- Get a report you can download or email to yourself, with how to fix each item.
Questions
Is it really free?
Yes. There is no sign-up and no card. You can email the report to yourself; we only contact you if you tick the box that says we may.
Do you keep my AWS keys?
No. The keys go over HTTPS to our scanner for this one scan. They are not saved or logged, and the page clears them as soon as the scan ends. Use a user with only the ViewOnlyAccess and SecurityAudit policies (root keys are refused), and delete the key afterwards or use temporary keys.
Can I try it without an AWS account?
Yes. Open the sample account to see a full report before you connect your own. Azure and Google Cloud are coming soon and show the sample for now.
What is the difference between the free tools and FreshField?
The free tools take one snapshot of your settings and files and give you a list to fix yourself. FreshField Runtime Intelligence watches your running application all the time, finds the cause with evidence down to the line of code, and hands your team a tested fix as a pull request.
Is my data stored?
No. Nothing you submit is stored: not keys, not the site, not the code, not results. Code and log files are read inside your browser and never uploaded.