1
@andriosrobert on Twitter
We've been building an access gateway for the past few years. The first version was built in Clojure, and we rewrote it in Golang. But that's a whole other story.
The gateway has a new type of architecture that allows packet manipulation (one of the reasons for Golang), which basically means you can programmatically change contents of connections in real-time.
Therefore it enables a whole set of problems to be consolidated at the access gateway layer, like data access policies (DLP), review of critical operations before they run (Change Management), automate repeat operations (Runbooks) and more. And this is how we monetize the solution.
Because of that we're open-sourcing the core of the gateway under MIT license. And we're including enterprise features from other gateways and some unique and new options enabled by our architecture.
Our vision for the project is to do what nginx did for HTTP to the protocols we interact with infrastructure.
It is early days and there's lots to do on the documentation side and making it easier to get started. We're working on these, but I'm super excited to share it with you.
Would love to hear any feedback, comments, critics, anything: https://github.com/hoophq/hoop
Teleport is great, paved the way for safer internet with its community edition for many years. It isn't without many drawbacks from their older architecture, like requiring certificates infrastructure. It was built before wide adoption of IDPs, resulting in a lot of unnecessary headaches with certificates to this day, even as IDPs already abstract these problems with their protocols. Despite the management overhead, Teleport was securing servers, containers, and databases access for many. But it just came to and end.
However, Hoopdev's access gateway has Packet Manipulation capabilities. Built on top of OIDC and OAuth 2.0, you achieve the same level of security but delegating certificates management to IDP services. But as the Teleport features are things we consider table stakes and basics of our tool, we're giving it for free.
We want to maintain the path for a safe internet paved even as Teleport starts charging small teams and raise prices on paid customers. We can afford to do that because Teleport features aren't our bread and butter.
Therefore even the Just-in-time access that is only available in Teleport Enterprise are table stakes for us, and are now part of our free solution.
But why? Because the Hoopdev gateway is past the basics of SSO and session recording. We can afford to do this because we make money with Package Manipulation features like live AI Data Masking, AI Copilot Query Builder, Privileged Action Review and secure execution, and many more.
Therefore if you're looking for an alternative to Teleport to stick to a free solution, give Hoopdev a try.
If you want to upgrade your Teleport setup, check out Hoopdev.
The simpler the task I'm working on, the higher the likelihood it gets it right. This is where I get the most benefit from Copilot, as I already understand what I'm coding, why I'm coding it, and how it should appear. Copilot sometimes saves me the 5-30 seconds it would take to write it manually. Over the course of a day, these saved moments add up.
But I always found myself turning to ChatGPT for help writing SQL. I would 1) run a query to get the schema. 2) Feed schema to ChatGPT. 3) Ask GPT to write my query. 4) Paste query into client. Solid results, but the workflow was not great with lots of copy and paste and multiple apps.
I work at Hoopdev, an infrastructure access gateway and we happen to have a build-in web client. Therefore our language server has a REST API that we could hook to GPT4. But our first attempt failed. We tried the Ask AI box UX, which only solved half the problem: providing the schema as context. Not getting the way was still missing. The bad suggestions required another prompt to get fixed.
Therefore we went on to build the copilot experience [0], but the opposite of Github copilot happened: most suggestions are good. This is because the only context for writing SQL is the database schema and what you want to do, all the model has to do is translate your english query to another language (SQL) using a small context (schema), as opposed to full codebases.
Hoopdev's client is web-based, because of that you can try it in 15 seconds. After signing up you get a demo Postgres ready to be queried in the web [1]. If you don't wanna sign up, run it yourself and use your own OpenAI keys [2]. Please let me know what you think. any feedback is welcome. Is this helpful? Do you know/use a better alternative for SQL?
0. https://hoop.dev/blog/introducing-an-ai-powered-query-builde... 1. https://hoop.dev/start 2. https://hoop.dev/docs/deploy/AWS
I’m Andrios, founder and CEO of Hoopdev, and am excited to show you our web database client with a Go-based language server that’s easy to use and built for teams. As of today, we’re launching our Free plan and anyone can start using it. It works with any browser.
Desktop database clients have always felt clunky to me. After 10 years of programming, I still find myself struggling with basic tasks—like securely configuring access or just trying to pull data from a different device. Every time I'm away from my main setup, it feels like I'm locked out of my own data. These hurdles slow me down and remind me why we need to push for web-based solutions that are not just powerful, but also intuitive and accessible right from the browser.
At Hoopdev we are building a Clojurescript client and Golang server that keeps what’s best about database clients while modernizing the experience in the web. We’ve built
1) Schema navigation and autocompletion that works with any db 2) Grouped outputs: so you can easily copy, search, and share query outputs 3) AI-powered Data Masking and Community-sourced Workflows [0]: so you can build your own middlewares 4) The ability to share your outputs with teammates: no more pasting long unformatted SQL into Slack 5) Runbooks: save your team’s common queries into a Git repo so your teammates can run them form a web form.
We built a new type of language server that runs on Kubernetes, it is a lightweight Golang GRPC proxy that can scan and modify layer 7 packets in real-time (this is what enables real-time AI data masking). UI uses Clojurescript. You can self-host the full solution.
Our business model is to make the database client so useful for individuals and small teams that their companies will want to pay for the team and security features. We will never sell your data.
You will notice that a log-in is required and that we do collect usage data and crash reports. We do so because we’re spinning up backend resources for each user and also to keep improving the product. We’ll soon allow users to opt out of usage data. You can see our privacy policy here [1].
It is early, but we are confident that even today the experience is meaningfully better than in many desktop database clients. Please give it a shot at Hoop.dev and let us know how it goes.
Follow us on Twitter [2]. Let me know what you think! Ask me anything!
[0] https://github.com/hoophq/plugin-secretsmanager [1] https://hoop.dev/docs/more/privacy-policy [2] twitter.com/twitter.com/hoopdotdev