Viewing a single comment thread. View all comments

yuvalsteuer OP t1_j2d6kzd wrote

I built haystack - natural language search engine for workplace technical knowledge.

My name is Yuval I've been a software engineer for a few years now,

A few weeks ago I was scrolling through confluence pages trying to find ssh connection details to our jenkins second integration machine for 40 minutes straight, later I discovered my co-worker slack'ed me the ssh connection string two months ago.

A week later I started working on haystack - a search engine for workplace apps, meant for finding secrets, credentials, connection details.. It enables you to search slack, confluence, jira, teams, jfrog, github, and email in one place.

It supports natural language queries so a query like: "how to connect to integ2 machine?" yields:

ssh -i private.pem ubuntu@ec2-integration2.eu-est-1.compute.amazonaws.com

Privacy?

haystack stores user data locally, so there's no security risk - only you have access to internal docs, I didn't want to deal with security compliance headaches caused from storing user data in the cloud.

Rolled it out to my co-workers a week ago and they thought it's a hit, so I'm planning on releasing it publicly on March 2023.

Early access

If you want to try it out before March 2023 - Available here

20

dev_LA t1_j2epm3x wrote

This looks really useful, can't wait to check it out!!

4

d_ed t1_j2dzw0g wrote

How does it get the data to index?

3

yuvalsteuer OP t1_j2e0i0f wrote

Haystack is exclusivly client side, it takes SSO token from the setup procedure (you signin through each 3rd party service you want to index) and queries the respective APIs (slack, confluence, gmail, etc...).

The SSO tokens are stored client side inside IndexDB API (meaning they don't exit your browser).

3