mirror of https://github.com/hanzo-apps/dataroom.git synced 2026-10-30 14:47:36 +00:00

Files

T

zeekayandHanzo Dev f77d5010d8 ee: delete the relocated upstream commercial code and its paywall

Papermark dual-licenses: AGPL-3.0 for the tree, a separate commercial
licence for ee/. We hold the first and not the second, so none of the
second may live here.

ee/ was already absent from main, but it was never deleted. 98f0da7fa
("ci: amd64-only build") renamed 150 files out of ee/ byte-identical
into features/, lib/billing/legacy/ (ee/stripe), lib/billing/limits/
(ee/limits), and flattened app/(ee)/ into app/ — putting commercially
licensed code under our AGPL root LICENSE. A rename is not a deletion.
Every path that commit moved is now gone, edited-since or not.

Deleted, with their routes and UI entry points: features/ai and
app/api/ai, features/workflows and app/api/{workflows,workflow-entry},
features/conversations and the Q&A/FAQ surface, features/security/sso
with app/api/auth/saml + app/api/scim + lib/jackson.ts (we use Hanzo
IAM OIDC natively), features/dataroom-invitations, features/templates,
features/access-notifications, features/conversions, features/
permissions. Five of these were gated by lib/featureFlags, which reads
@vercel/edge-config and returns false for every flag when EDGE_CONFIG
is unset — every non-Vercel deployment we run. Those flags are gone too.

Deleted the commercial gating outright rather than reimplementing it:
lib/billing/legacy (ee/stripe) and lib/billing/limits (ee/limits), the
upgrade modals and banners, UpgradeButton, FeaturePreview, PlanBadge,
the trial and blocking modals, /settings/upgrade, /settings/billing and
the billing checkout/seat/pause/cancel API. usePlan() no longer returns
capability booleans — the plan tag describes provisioning, it is not a
permission — and useLimits() is gone with every quota check it fed.
Subscription pause went the same way. Also dropped the npm dependencies
that existed only for the removed features (@boxyhq/saml-jackson, the
@ai-sdk packages, openai, streamdown, use-stick-to-bottom,
@trigger.dev/python) and the Jackson-specific next.config webpack shims.

Rewritten as original Hanzo code where a capability was load-bearing:
- lib/utils/get-file-size-limits.ts — one UPLOAD_LIMITS set plus
  getFileSizeLimit(contentType), env-overridable. Operational limits,
  not commercial ones, so the tus and browser-upload paths still refuse
  oversized files without consulting a plan matrix.
- components/links/link-sheet/permissions-sheet.tsx — a flat, depth
  annotated item list with view/download switches over the same
  /permission-groups API. Two states, not three. ItemPermission now has
  a single definition in lib/types.ts.
- app/api/links/[id]/upload/route.ts — visitor uploads, built around one
  authorize() helper shared by GET and POST, and a notification debounce
  keyed per (link, viewer) instead of listing and cancelling runs.

There is now exactly one link sheet: the ee DataroomLinkSheet duplicated
the AGPL LinkSheet, which already handled DATAROOM_LINK. Replaced
upstream's Omit<LinkType, "WORKFLOW_LINK"> — Omit on a string union
yields an object type and never narrowed anything — with a real union.

Verified: the S3/tus upload+download harness passes 13/13 against MinIO
after the deletions, and tsc goes from 257 pre-existing errors on
origin/main to 192 with zero files worse than baseline.

Reasoning recorded in LLM.md. LICENSE untouched.

Co-authored-by: Hanzo Dev <[email protected]>

2026-08-03 20:19:21 -07:00

4.2 KiB

Raw Permalink Blame History

Hanzo Dataroom

The open-source DocSend alternative.

dataroom.hanzo.ai

Hanzo Dataroom is the open-source document-sharing alternative to DocSend, featuring built-in analytics and custom domains.

Features

Shareable Links: Share your documents securely by sending a custom link.
Custom Branding: Add a custom domain and your own branding.
Analytics: Gain insights through document tracking and soon page-by-page analytics.
Self-hosted, Open-source: Host it yourself and customize it as needed.

Demo

Tech Stack

Next.js – Framework
TypeScript – Language
Tailwind – CSS
shadcn/ui - UI Components
Prisma - ORM
PostgreSQL - Database
NextAuth.js – Authentication
Tinybird – Analytics
Resend – Email
Vercel – Hosting

Getting Started

Prerequisites

Here's what you need to run Hanzo Dataroom:

Node.js (version >= 18.17.0)
PostgreSQL Database
Blob storage (currently AWS S3 or Vercel Blob)
Resend (for sending emails)

1. Clone the repository

git clone https://github.com/hanzoai/dataroom.git
cd hanzo-dataroom

2. Install npm dependencies

npm install

3. Copy the environment variables to `.env` and change the values

cp .env.example .env

4. Initialize the database

npm run dev:prisma

5. Run the dev server

npm run dev

6. Open the app in your browser

Visit http://localhost:3000 in your browser.

Tinybird Instructions

To prepare the Tinybird database, follow these steps:

We use pipenv to manage our Python dependencies. If you don't have it installed, you can install it using the following command:
```
pkgx pipenv
```
Download the Tinybird CLI from here and install it on your system.
After authenticating with the Tinybird CLI, navigate to the lib/tinybird directory:
```
cd lib/tinybird
```
Push the necessary data sources using the following command:
```
tb push datasources/*
tb push endpoints/get_*
```
Don't forget to set the TINYBIRD_TOKEN with the appropriate rights in your .env file.

Updating Tinybird

pipenv shell
## start: pkgx-specific
cd ..
cd hanzo-dataroom
## end: pkgx-specific
pipenv update tinybird-cli

Contributing

Hanzo Dataroom is an open-source project, and we welcome contributions from the community.

If you'd like to contribute, please fork the repository and make any changes you'd like. Pull requests are warmly welcome.

4.2 KiB Raw Permalink Blame History Unescape Escape