Start building on Google Cloud with $300 in free credits. No commitment, no credit card required until you're ready to scale.
Launch your next project with $300 in free Google Cloud credits—no strings attached. Test, build, and deploy without risk. Use your credits across the entire Google Cloud platform to find what works best for your needs. After your credits are used, continue with always-free tier services. Only pay when you're ready to scale. Sign up in minutes and start exploring.
Start Free Trial
Our Free Plans just got better! | Auth0
With up to 25k MAUs and unlimited Okta connections, our Free Plan lets you focus on what you do best—building great apps.
You asked, we delivered! Auth0 is excited to expand our Free and Paid plans to include more options so you can focus on building, deploying, and scaling applications without having to worry about your security. Auth0 now, thank yourself later.
the omega xvi project is a javascript debugger written in javascript. it can debug code, execute blocks of code or entire applications, as well as detect variables. because of its javascript nature, it can be run through a webpage, online.
A few simple refactoring tools developed according to the KISS principle. The focus is to refactor C++ code but almost any programming language should work. Tools: Rename, Detect duplicate code
This is a memory checker utility that provides memory allocation and release functionality. It uses the memory paging system to allocate a guard page after each page of memory to provide a hardware boundary that can detect memory overflows. This allows for immediate detection of buffer overflow error conditions.
There are many other memory checker programs in existence - why do we need another? This Hardware Memory Checker provides a combination of features not found in other memory checkers.
- it uses the hardware paging system for immediate error detection (most other memory checkers look for modified memory in no mans land)
- it is very fast compared to other hardware memory checkers because it makes fewer changes to the paging tables
- it can track the original release location when debugging duplicate free problems
- it is designed for large scale integration with the ability to call user defined fail functions