Model or dataset
xynehq/xyne avatar
xynehq/xyne

xyne: the README says it moved to another organisation, the last push was yesterday, and the last release is from 2025

AI-first Search & Answer Engine for work. Open-source alternative to Glean.

698 stars71 forksTypeScriptApache-2.0

At a glance

What is it?
A TypeScript search and answer engine for workplace data, self-hostable and permissions-aware, whose own first line declares the repository unmaintained and points at a new home under a different organisation. Its pitch names Slack and Atlassian as connected apps while the feature section lists them as next.
Who is it for?
Decide which repository you are actually adopting before you read anything else, because the README's first line points at a different organisation's project and none of the documentation links follow it: every guide, quickstart and deployment page still resolves through the old docs domain. If you are starting fresh, follow that pointer rather than this tree.
Can I use it commercially?
Yes. Apache-2.0 is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 6 days ago.
What is it written in?
Mainly TypeScript, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • xynehq/xyne698 ★ · +17
Star history
Repository2026-09-112026-11-15
xynehq/xyne681698

17 Stars in the last 65 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

The first line of the README says this repository is no longer maintained here

Before the badges and before the product description, the document announces a move: a moved notice, followed by a new home pointing at github.com/juspay/xyne-spaces. That is a different organisation from the one hosting this repository, so the project has changed hands or been re-homed rather than merely forked. Everything after that line continues to describe the product as if it lived here, including the badge that points at this repository's releases page and the Slack invite for contributors. The state of the repository itself is more ambiguous than the notice: it is not archived, its default branch is main, and its last push is dated 2026-10-01, one day before this check. So commits are still landing here while the document tells readers to go elsewhere. Neither fact cancels the other, and a reader has to hold both.

One release, tagged v3.1.1 on 2025-09-30, against commits from this week

The release history holds a single entry, v3.1.1, dated 2025-09-30. That is more than a year before the current date, and it sits against a repository whose last push is 2026-10-01. The gap has a practical consequence for anyone pinning dependencies: there is no tagged version that contains the recent work, so a version-based install gets you a year-old snapshot while the branch is somewhere else entirely. For a self-hosted platform the version number also does less work than usual, because the deployment is a container built from source rather than a published package. The repository carries a Renovate configuration, which suggests dependency updates are automated, and a Husky directory, which suggests commit hooks, but neither of those produces a release. Nothing in the visible text explains why releases stopped.

Slack and Atlassian appear in the pitch and in the list of things not built yet

The introduction states that Xyne connects to your applications, naming Google Workspace, the Atlassian suite, Slack and GitHub, and then says it securely indexes your data and maps a graph of relationships. Later, under a heading about what is live, the scope is narrower: entire Google Workspace, meaning not just drive, PDFs, docs, sheets and slides but also calendar, contacts and gmail including attachments. Then a single line reads NEXT with Slack and Atlassian integrations. So the two applications named first in the pitch are the two listed as future work. The text is pointed about this in the Google paragraph, noting that most enterprise search products claim Google Workspace integration while quietly meaning drive alone and skipping contacts, calendar and mail, which suggests the authors were aware of the gap and wanted to be the ones covering it. GitHub is named in the pitch and never mentioned again.

A single docker-compose command is promised, and no compose file sits at the root

The deployment section says Xyne can be run locally or deployed to a virtual machine using a single docker-compose command, then declines to give the command. It redirects to documentation instead: a Quickstart page for local use and a Cloud Deployment page for AWS EC2. The root listing does contain a Dockerfile, a second Dockerfile named for Vespa, a start.sh, a start-aws-linux.sh and a deployment/ directory, so the artefacts for a container deployment exist. What is not at the root is a compose file. One may sit inside deployment/, which the listing does not describe, but the visible text does not say so, and the phrase single command is doing work that the repository root does not support on its own. The two start scripts, one generic and one for AWS on Linux, hint that the same bring-up differs per platform.

The image build tolerates a missing init script and leaves data restore commented out

Two lines in the Dockerfile describe things that are optional, which is worth knowing before you trust a built image. The first makes an init script executable with `RUN chmod +x docker-init.sh 2>/dev/null || true`, so if that file is absent the build continues silently instead of failing, which means an image can come out without whatever initialisation that script was supposed to do. The second pair of lines, which would copy a data restoration script and make it executable, is commented out entirely, so restoring data is not part of the image build at all. Both choices are defensible for a development-oriented image, and both mean the same thing to an operator: the image you build is not self-sufficient, and the missing pieces have to be supplied by whatever is orchestrating it.

The image is linux_amd64 only and fetches a pinned Vespa CLI tarball at build time

The build starts from the official Bun 1 image and installs dependencies twice, once for the server and once for the frontend, which keeps layer caching effective. It then switches to root to install system packages, and the list is long and specific: wget, curl, tar, expat and its headers, plus a full graphics stack of cairo, pango, jpeg, gif, rsvg, pixman, fontconfig and freetype headers. That stack is there for rendering, which fits an engine that produces answers and previews from indexed documents. The retrieval engine arrives separately, as a download of the Vespa CLI for release v8.453.24 as a linux_amd64 tarball, unpacked and moved to /usr/local/bin, then the package cache is cleaned. Two consequences: the image is pinned to one architecture and one platform, so building it on an Apple silicon machine is not the path this file supports, and the build depends on a third-party release URL resolving at build time.

Every documentation link still points at the old domain while the code moved

The links out of this repository are all internal to it. Documentation is at docs.xynehq.com, and that host serves the authentication guide for Google service accounts, the quickstart, the AWS EC2 deployment page, and the contribution guide. The product page is at xyne.ai and the two demos are hosted on YouTube, one for the search and answer engine and one for DeepSeek running over internal data. None of these references the new home named at the top of the document. So a reader who follows the move notice arrives at a new repository, and a reader who follows any documentation link arrives at pages still served from the old domain. Which of those is maintained, and whether the guides describe the code in the new home, is not stated anywhere in the visible text.

Five feature claims, and one of them comes with a mechanism

The feature list is five items, and they are worth separating by how much they commit to. Self-hosted is concrete: deploy on a laptop, on premises or in the cloud, and the Dockerfile supports that claim. Model agnostic is concrete too, naming any LLM, any cloud provider, and a local Deepseek served through ollama, which means the gateway is genuinely in the path rather than a fixed vendor call. Permissions-aware is the claim with a mechanism behind it: live enforcement of your applications' existing permissions, so nobody sees what they do not already have access to, which for a Workspace deployment means the service account setup matters as much as the index. High performance is asserted with one line, multi-threaded data ingestion. Private and secure is asserted as no training on your data or prompts and no telemetry, both of which are promises about behaviour rather than configurations you can inspect.

Editorial conclusion

Decide which repository you are actually adopting before you read anything else, because the README's first line points at a different organisation's project and none of the documentation links follow it: every guide, quickstart and deployment page still resolves through the old docs domain. If you are starting fresh, follow that pointer rather than this tree. If you are pinned here, the honest state is that one release exists, v3.1.1 from 2025-09-30, while the branch itself was pushed on 2026-10-01, so commits are landing without tagged releases and you should pin a commit rather than a version. Two more checks. Integration coverage is narrower than the pitch: Google Workspace is described as live, Slack and Atlassian as next. And the deployment promise of a single docker-compose command has no compose file at the root, only a Dockerfile pinned to linux_amd64 that installs the Vespa CLI, so budget for building the image yourself rather than pulling one.

Frequently asked questions

Where has Xyne moved to?

The README opens with a moved notice saying the repository is no longer maintained here, and gives the new home as github.com/juspay/xyne-spaces. The repository itself is not archived, its default branch is main, and its last push is dated 2026-10-01.

Which applications does Xyne actually connect to?

Google Workspace is described as live, covering drive, PDFs, docs, sheets, slides, calendar, contacts and gmail with attachments, set up through a service account integration. Slack and Atlassian are listed as next, even though the introduction names them among the connected applications.

How do I deploy Xyne?

The README says it runs locally or on a virtual machine with a single docker-compose command, then points to the Quickstart docs for local use and the Cloud Deployment docs for AWS EC2. The root has a Dockerfile, a Dockerfile-vespa, start.sh and start-aws-linux.sh, but no compose file at the root.

What license is Xyne released under?

Apache-2.0, and both sources agree on it. A LICENSE file sits at the root of the tree, the README carries the Apache-2.0 badge, and the repository's license field reads the same. The only release published is v3.1.1, dated 2025-09-30.

What does Xyne say about models and about using your data?

It is described as model agnostic, plugging into any LLM or cloud provider, including a local Deepseek served through ollama. On data it states no training on your data or prompts and no telemetry, and claims permissions are enforced live from your applications rather than reimplemented.

Official sources

  1. License: Apache-2.0
  2. Project website
  3. README
  4. Releases
  5. xynehq/xyne on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/xynehq-xyne.svg)](https://hysenlabs.com/projects/xynehq-xyne)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/xynehq-xyne.svg)](https://hysenlabs.com/projects/xynehq-xyne)

Was this useful?