harshithmul

7 ms·

61.
by harshithmul 2y ago
We also plan to build an integration with JIRA where you can still use JIRA and link the issues in Tegon as you slowly migrate to our product. Similar to Github issues which is already live.
62.
by harshithmul 2y ago
We've already transitioned few private beta customers from JIRA using a backend script. Although we haven't addressed all edge cases yet, we anticipate that this script will evolve over time. Once we've covered a sufficient n
63.
by harshithmul 2y ago
Yes, we pledge to remain open source. 1. Our design is inspired by the linear UI, which we believe is the best. We didn't want to reinvent this aspect. 2. As for our differentiation, we've been building the system for two months a
64.
by harshithmul 2y ago
Thank you. We chose open source for several reasons: 1. We are building for Engineering Teams: Being in the public domain allows us to collaborate openly with engineering teams and build a better product. 2. Building Trust in AI Agents: Tru
65.
by harshithmul 3y ago
How Plaid has provided all needs for Finance products by providing unified API we are bringing that to multiple verticals. And choosing LLMs as our primary ICP, the solution will evolve more for their needs.
66.
by harshithmul 3y ago
We haven't gotten into finance integrations yet but would love to understand use case more and see what we can do. Happy to discuss more in our community Slack. Also what kind of SAAS sources are currently ingesting?
67.
by harshithmul 3y ago
Would love to understand why you think so?
68.
by harshithmul 3y ago
There are 3 major challenges 1. We think the context you want is distributed into multiple APIs in most of cases and there are also multiple APIs on which you might want to search. Ex: Users, Tickets, Comments etc. A lot to build from scrat
69.
by harshithmul 3y ago
We took the first/3rd meanings https://www.wordhippo.com/what-is/another-word-for/poozle.ht... but missed in between :(
70.
by harshithmul 3y ago
Would love to understand if there is something missing.
71.
by harshithmul 3y ago
Gotcha. We will surely rethink on the name
72.
by harshithmul 3y ago
Yeah we will be opensourcing this in the coming week. Happy to answer questions. Feel free to join our Slack we can discuss this there or shoot me an email at harshith[@]poozle.dev
73.
by harshithmul 3y ago
Yeah :( looks like we should change the name
74.
by harshithmul 3y ago
As we currently expose the common models APIs and you can use certain transformations before you send them into the VectorDB. This way you just have to write one transformation for all the SAAS tools in a specific category. We are having ve
75.
by harshithmul 3y ago
Got it. We might have to think to change the name
76.
by harshithmul 3y ago
Yeah true. We will pull all similar tickets from multiple SAAS tools and send them back in a common ticketing model
77.
by harshithmul 3y ago
gotcha. We do the ETL in the background and ensure that the model is completed irrespective of the 1-1 or different entity. You would also be doing the same if you manage the ETL. You could check ( https://github.com/poozlehq
78.
by harshithmul 3y ago
> If one service's entity has X field, but all the others don't, do you include it or not? We have a raw field from which you can pick anything integration specific.
79.
by harshithmul 3y ago
Yeah, I think we have 2 things here. Take an example model a "Ticket". 1. Dealing with custom fields. We provide a way you can map the custom fields specific to the company into the common Model. 2. Dealing with the naming differe
80.
by harshithmul 3y ago
It's most commonly used in NZ. It means to scavenge for collectable objects. But yeah that's the start but later we realised it was also something else.
81.
by harshithmul 3y ago
We are more into unified API with the right tooling needed for LLMs to talk to these SAAS tools whereas Gorilla is a model which has knowledge about APIs. More than a similarity we thought we could use the gorilla LLM knowledge to get to a
82.
Show HN: Poozle – open-source Plaid for LLMs(github.com)
132 points by harshithmul 3y ago|39 comments
83.
by harshithmul 3y ago
Hey yeah we were working on it but after some user research, we think there is a lot of friction and not much of market there. We are pivoting to something new and we are evaluating these.