Composio | Senior Backend Engineers + Product Engineers (Frontend + SDKs) | Full-Time | In Office (SF and Bengaluru, India)
Hi HN, we’re building https://composio.dev
— the fastest way for AI agents and developers to take action across apps like GitHub, Gmail, Slack, and more. Our SDKs (TypeScript + Python) and APIs let developers connect and execute tools in just a few lines of code.
We’re a small, fast-moving team obsessed with developer experience. Our stack is TypeScript-heavy: backend in TS/Go/Python, frontend in React/Next.js, SDKs in TS/Python. You’ll work across product and engineering to define APIs, craft abstractions, and ship features used by thousands of developers.
We’re early stage, small team and looking for engineers who want ownership and impact.
Feel free to reach out to me with your resume and links of your work: [email protected]
I'm working solo on a project called Sequel (https://sequel.sh), it uses the latest Claude 3.7 to generate and execute SQL query against your connected database. Used by a bunch of folks now, trying to figure out a distribution channels and setup to self host the tool now.
- Led the development of AI-driven workflows and geospatial visualization platforms at Locale.ai, handling real-time data from IoT devices, GPS, and more.
- Built Sequel.sh, a tool that translates natural language into SQL for database querying and visualization.
- Developed tools like Apico.dev, a no-code API builder, and Streamon, an open-source streaming bridge for Instagram with 300K+ downloads.
What I’m Great At:
- Frontend: Vue.js, React, Next.js, and state management tools like Vuex, Pinia, and Zustand.
- Visualization: Tools like D3, DeckGL and Mapbox for handling massive datasets.
- Design: I can craft beautiful interfaces, you can check my works on dribbble (https://dribbble.com/haxzie)
What I’m Looking For:
I’m excited to join a product-obsessed team tackling challenging problems with creativity and data. I thrive in small, collaborative teams and love working on tools that empower users.
I'm building https://sequel.sh it's an AI data analyst and text-sql interface which helps you query data, generate charts and analyse the data to give insights all without a single line of SQL.
Give it a try and you would know the difference between AI integrated with Supabase and Sequel. We are more focusing on the BI space, and dashboarding. Which quite far away from what Supabase or Table Plus is and is targeted towards analysts.
At some point, sequel can replace TablePlus witha few new features coming soon, along with a desktop app.
Wow, thank you for taking your time to go through the app!
2. Will fix the docs to work on mobile screens, this was a last moment run to setup docs, wanted to try it without any templates. Have to manually handle the responsiveness now :)
3. Makes sense, this shouldn't have caused issues on mobile. Thanks for letting me know.
4. Midjourney did a pretty good job with the images, got em done within no time! haha
---
Visualisations are done using recharts. Currently I have implemented a very limited set of charts, hopefully will add more with much more customizability.
I am planning on opensource the product soon, going ahead with an open core model, and a self hosted version along with it.
The concern about LLM providers makes sense, will add them to the docs as well.
Currently there is no hard wired instructions to not let the LLM insert/drop it. It's all as good as the user instructing it to do something and it does. There are soft instructions to not generate queries for that, but it's as good as telling a kid not to eat chocolates. I am planning to run a post analysis on the queries generated and marking them as potentially dangerous, so that the queries don't get executed automatically, but with a confirmation from the user. This should ideally be separate from the actuall LLM which generates the query.
Again, thank you so much for the valuable feedback. This helped me a lot!
Hey, I'm a senior fronted engineer with focus on product and design. I have worked with multiple early stage startups to go from 0-launch. My expertise lies in architecting data intensive applications, elegant design, and product maangement. I have professional experience in design, frontend and backend work. One the side, I build a bunch of tools to solve problems, some of them are (https://apico.dev, https://krata.app, https://snipp.in and a lot more). I'm open to working with small/early teams who are product focused.
This is pretty neat! I had built snipp.in to solve my own problems with other note taking app. It works completely offline + looks a lot like VS code for folks who love using .txt files
Hey, I was building something similar a while back for a specific usecase around shopify stores. Wondering is this a sustainable business and how long have you been running this for?
This is wonderful feedback! Will try to fix some of these soon, thanks. The project was built around 2 years ago, but it failed in giving any signs of generating revenue. It was abandoned for a while, I shut down the cloud version and open sourced part of the codebase.
Creator of Apico here. This is a tiny example of how to use SaaS apps as backend for your small projects. As folks outlined in other comments I will clarify a few things.
> How is this different from using the SDKs, or APIs directly from Google?
Honestly it's very similar, the APIs offered by this app and Google are very similar. The only difference is that you get the APIs literally within a single click and added benefit of fine-grained access control over individual endpoints. You can make endpoints public (access to anyone) vs private (only be accessed with an auth token)
> Why don't just use Google APIs then?
Most of the APIs are server side considering security, you cannot expose these credentials to the client side, unless you only allow specific scopes that can be exposed. And then create a different set of credentials to be used on your server side to handle other actions. With this app, it acts as a proxy and firewall on top of the Google APIs, so you can expose specific endpoints to be public and rest to be private.
Adding to that you need to spend more time looking through docs and setting up Postman or similar tool to test the APIs, the app literally gives everything you need, APIs, Playground and a proxy for you to play around.
> Rate limits?
Right now, I haven't looked into this, but hopefully soon :)
This is pretty cool. Quite similar to the solution I have posted. The actual benefit comes when you use it for other APIs, because the app allows you to setup access control rules over individual endpoints, so that you can expose endpoints to frontends and no-code apps without worrying about security.
This is exactly similar to using google APIs as well, just that you are exposing the credentials client side unless you are planning to put the logic on server. With this service you can only allow read APIs and block write APIs, similar to scopes. But you get the APIs within just a few clicks with an API playground and proxy with additional security.
Probably with all the LLMs out there and AI gadgets popping out, it wouldn't be too far to have a new kind of Human Computer Interaction Interface, maybe not voice, but maybe even thoughts or some sort of new ways of interactions, subtle but way more context aware and versatile with the amount of input required to be very very less.
The Instagram API lands in a very gray area, so as the whatsapp API as well. Personally working with reverse engineered Instagram APIs, A.K.A private APIs, There are high chances of accounts getting banned immediately after using these APIs for automation.
How do you plan on sustaining such a project for a long time when you can be easily killed by the platform and pose potential risk to the users?
(I had to shutdown a service used by 100K+ users due the same reason)
Two things I have seen most of the really good programmers I have known. One, they read a lot of code, they mostly spend time digging into open source codebases and quite a lot of time contributes to them as well, which goes to the second point. Two, getting your code reviewed by a lot more programmers, with more experience than you, you get a much better perspective on a lot of things.
Hi HN, we’re building https://composio.dev — the fastest way for AI agents and developers to take action across apps like GitHub, Gmail, Slack, and more. Our SDKs (TypeScript + Python) and APIs let developers connect and execute tools in just a few lines of code.
We’re a small, fast-moving team obsessed with developer experience. Our stack is TypeScript-heavy: backend in TS/Go/Python, frontend in React/Next.js, SDKs in TS/Python. You’ll work across product and engineering to define APIs, craft abstractions, and ship features used by thousands of developers.
We’re early stage, small team and looking for engineers who want ownership and impact.
Feel free to reach out to me with your resume and links of your work: [email protected]