Show HN: Poozle – open-source Plaid for LLMs

This page summarizes the projects mentioned and recommended in the original post on news.ycombinator.com

SurveyJS - Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App
With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
surveyjs.io
featured
InfluxDB - Power Real-Time Data Analytics at Scale
Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
www.influxdata.com
featured
  • poozle

    A single API for product integrations

  • We do the ETL in the background and ensure that the model is completed irrespective of the 1-1 or different entity. Anyways you would also be doing the same.

    Also if you need more customization you can write on top of the integration we have already (https://github.com/poozlehq/poozle/tree/main/integrations/ti...) and plug it into the platform.

  • gorilla-cli

    LLMs for your CLI

  • Very cool product! Have you consider relying on Gorilla for integrations?

    https://github.com/gorilla-llm/gorilla-cli

  • SurveyJS

    Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.

    SurveyJS logo
  • gorilla

    Gorilla: An API store for LLMs

  • nango

    A single API for all your integrations.

  • Definitely a difficult problem you're taking on here, but I don't see anything specific to LLMs here? How or why are you marketing towards LLMs?

    How do you compare to the larger players here already Nango[0] and Merge[1] ?

    I'm curious how you're thinking about data access / staleness? It's great that you're handling the oauth dance, but does that mean every end user of the product has to auth every product they interface with or are you handling this all at the super admin / enterprise level?

    Right now I think there's too much emphasis on the "data loading" aspect of LLMs. I expect to see a swing back into using 3rd party API's SDKs. Interested to hear your thoughts on the Google API, it's absolutely massive and trying to shoehorn that into a unified API scares me.

    The only real player that I could see to launch something like this and be successful is Okta.

    [0] - https://github.com/NangoHQ/nango

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts

  • Show HN: Revert – open-source unified API for product integrations

    4 projects | news.ycombinator.com | 24 Oct 2023
  • Ask HN: Suggest open source alternative to Unified API providers like Merge.dev

    2 projects | news.ycombinator.com | 8 May 2023
  • Why is OAuth still hard in 2023?

    3 projects | /r/programming | 26 Apr 2023
  • Buy vs. Build: Share your journey on choosing between purchasing or developing integration components

    2 projects | /r/SaaS | 19 Apr 2023
  • Nango

    1 project | /r/devopspro | 2 Mar 2023