FuelCloud is a fuel technology company building the future of Fuel Management Systems for monitoring and managing bulk fuel supplies. By combining four generations of fuel industry knowledge with the latest innovations in cloud computing and mobile technology, FuelCloud's Fuel Management Systems deliver cardlock-level control at backyard prices. The result is a powerful yet affordable Fuel Management System that protects fuel from loss and theft, streamlines reporting and management, and puts you in control of your fuel.
The heart of FuelCloud's system is the cloud-based web portal. From the web portal, managers can track transactions and tank volumes, control who can access fuel (and how much they can have), and automate creating and delivering reports The web portal also integrates your bulk fuel data with your other fleet and business management software, helping to create a complete data picture of your fleet operations from tank to tailpipe.
Learn more

Compliance work eats engineering time. Hyperproof exists to give that time back by automating the parts of GRC that don't need a human: pulling evidence out of GitHub, Jira, ServiceNow, Snyk, and cloud storage on a schedule, running recurring tests against high-frequency controls, and kicking off a task automatically the moment something fails instead of waiting for the next audit cycle to find out.
Under the hood, Hyperproof maps one control to 160+ frameworks (SOC 2, ISO 27001, HIPAA, NIST, and others), so a control tested once can satisfy several standards instead of forcing teams to rebuild the same work per framework. AI agents handle the first pass on evidence review and gap-flagging, leaving humans to make the actual judgment calls rather than hunting down documentation.
Teams using it report cutting audit prep by roughly 350 hours a year, a 66% drop in duplicate controls, and about $150K saved annually on control orchestration. It also scales to messier org charts, with the ability to scope controls by business unit or entity instead of flattening everything into one program.
Built in 2018 out of the Seattle area, Hyperproof is used by engineering and security-heavy orgs like Reddit, Fortinet, Appian, and Outreach that are tired of treating compliance as a manual, spreadsheet and email process and want it to run more like the rest of their infrastructure: automated, monitored, and auditable.
Learn more
Inertia
Inertia.js serves as a framework that empowers developers to create contemporary single-page applications by utilizing traditional server-side routing and controllers. It facilitates the development of fully client-side rendered SPAs while simplifying the complexities often associated with such applications. By eliminating the need for client-side routing or an API, Inertia.js enables developers to continue using familiar controllers and page views. Acting as a bridge between server-side frameworks and modern frontend technologies, it provides official client-side adapters for React, Vue, and Svelte, alongside server-side adapters for Laravel, Rails, and Phoenix. This unique methodology allows for the creation of modern SPAs while capitalizing on existing server-side conventions. Importantly, Inertia is not intended to replace current server-side or client-side frameworks; instead, it is designed to complement them. You can think of Inertia as the essential connector that unifies the two realms of web development. Through its use of adapters, Inertia simplifies the process and enhances the overall development experience. By leveraging this framework, developers can enjoy the best of both worlds while maintaining efficiency and familiarity in their workflow.
Learn more
Giotto
The framework operates on the principles of Model, View, and Controller architecture. It prioritizes a structured approach that leads to code that remains easy to manage over time. In contrast, many widely-used web frameworks focus on rapid launch capabilities, often resulting in code that may deploy swiftly but becomes increasingly complicated after numerous updates. For instance, processes like Apache and Gunicorn serve as examples of controller operations. When initiated, a controller process receives a manifest, which acts as a roadmap. All requests directed towards the controller process are then navigated to a specific program outlined in the manifest. Essentially, a manifest is a compilation of various programs that can be executed. Users can interact with the controller process through web requests, command line inputs, or other actions, showcasing its versatile handling capabilities. This system underscores the importance of a well-organized structure in software development.
Learn more