eulercoder | 1 month ago | on: Meta shut us down. LinkedIn took us to court. We're still building
eulercoder's comments
eulercoder | 1 year ago | on: Show HN: Hyperbrowser – Scalable Browser Infrastructure for AI Apps
eulercoder | 1 year ago | on: Show HN: Hyperbrowser – Scalable Browser Infrastructure for AI Apps
This looks very interesting and I’d love to try it.
We have data extraction and enrichment platform. We process over 12 million automations for our users, half of this is done on lambda and rest we try to process in a container.
We also utilize 10 GB+ in proxies.
I tried to do all the math on how much it would cost on your platform if we do a pilot project but I’m so confused with the pricing.
Can you please explain for 10,000 hours and 10 GB proxy usages what would the cost?
eulercoder | 3 years ago | on: Show HN: Unriddle – Create your own GPT-4 on top of any document
I couldn’t find any information about pricing? This is going to be a free tool?
eulercoder | 3 years ago | on: Launch HN: Astro (YC W21) – Build your own dev teams in Latin America
eulercoder | 4 years ago | on: Show HN: I made a Chrome extension that can automate any website
We are building similar tool at TexAu and would love to catch-up with you sometime this or next week!
@iamvikeshtiwari on Twitter
eulercoder | 4 years ago | on: Show HN: I made a Chrome extension that can automate any website
Bardeen looks super look, we are also building something very similar but very much focused on Web Automation, you can build cross platform automations on TexAu - https://texau.app
I’m thinking we should integrate with Bardeen and it will be open up so many more possibilities
~ Vikesh
eulercoder | 8 years ago | on: Ask HN: Who is hiring? (December 2017)
Thank you! :)
eulercoder | 8 years ago | on: Ask HN: Who wants to be hired? (December 2017)
Remote: Yes
Willing to relocate: No
Technologies: NodeJs (Core Member of NodeJS), React, Meteor, Python, React, AWS, Chatbots (Worked at Slack in SF), Automation, Scripting
Résumé/CV:
https://gist.github.com/vicky002/92e7a1e3d6e058d40b1c54d3abe...
Email: [email protected]
eulercoder | 8 years ago | on: AlgoWiki: Repository of resources on different topics of computer science
eulercoder | 8 years ago | on: AlgoWiki: Repository of resources on different topics of computer science
Websites will have categories and global search so you can find anything you are looking for quickly.
eulercoder | 8 years ago | on: AlgoWiki: Repository of resources on different topics of computer science
eulercoder | 8 years ago | on: AlgoWiki: Repository of resources on different topics of computer science
Should I change the title or something like that?
eulercoder | 8 years ago | on: AlgoWiki: Repository of resources on different topics of computer science
Be sure, I will compliers, robotics and hardware stuff very soon.
eulercoder | 8 years ago | on: AlgoWiki: Repository of resources on different topics of computer science
A few things the post doesn't cover that might be useful context:
What we got wrong with V1 and V2. We built a browser automation tool that depended entirely on platforms we didn't control. That's an obvious mistake in hindsight, but at the time, every company in our space was doing the same thing. The C&Ds were inevitable. We just didn't want to see it.
Why we chose a spreadsheet interface for V3. We tested three approaches: a workflow builder (what V2 was), a dashboard UI, and a spreadsheet. The spreadsheet won because our users already think in rows and columns. Every agency we talked to was exporting CSVs from 4 different tools and joining them manually in Google Sheets. We realized the spreadsheet IS the workflow, not a step in one.
*Where we are financially*. 25 people, bootstrapped, no VC. We've been close to zero runway multiple times. V3 is live with paying customers but we're early. I won't pretend otherwise.
*What I'd love HN's input on*. We're building waterfall enrichment across multiple data providers with stop-on-success logic and AI columns that run LLM calls per row. If anyone here has dealt with similar orchestration problems at scale (provider failover, cost optimization across APIs, batching LLM calls), I'd genuinely love to hear how you approached it.
Ask me anything about the legal battles, the tech, building B2B from India without venture money, or where we screwed up.