Documenso Logo

The Open Source DocuSign Alternative.
Learn more »

Discord · Website · Issues · Roadmap

Join Documenso on Discord Github Stars License Commits-per-month

> 🦺 Documenso 1.0 is deployed to our Staging Environment. > > The code can be found on the [feat/refresh](https://github.com/documenso/documenso/tree/feat/refresh) branch. > > The new version will be released after the current testing phase. # Join us in testing Documenso 1.0 during [MALFUNCTION MANIA](https://documenso.com/blog/malfunction-mania)
## About this project Signing documents digitally is fast and easy and should be the best practice for every document signed worldwide. This is technically quite easy today, but it also introduces a new party to every signature: The signing tool providers. While this is not a problem in itself, it should make us think about how we want these providers of trust to work. Documenso aims to be the world's most trusted document-signing tool. This trust is built by empowering you to self-host Documenso and review how it works under the hood. Join us in creating the next generation of open trust infrastructure. ## Recognition Documenso - The open source DocuSign alternative | Product Hunt Documenso - The Open Source DocuSign Alternative. | Product Hunt ## Community and Next Steps 🎯 We're currently working on a redesign of the application, including a revamp of the codebase so Documenso can be more intuitive to use and robust to develop upon. - Check out the first source code release in this repository and test it - Tell us what you think in the [Discussions](https://github.com/documenso/documenso/discussions) - Join the [Discord server](https://documen.so/discord) for any questions and getting to know to other community members - ⭐ the repository to help us raise awareness - Spread the word on Twitter that Documenso is working towards a more open signing tool - Fix or create [issues](https://github.com/documenso/documenso/issues), that are needed for the first production release ## Contributing - To contribute, please see our [contribution guide](https://github.com/documenso/documenso/blob/main/CONTRIBUTING.md). ## Contact us Contact us if you are interested in our Enterprise plan for large organizations that need extra flexibility and control. Book us with Cal.com ## Tech Stack - [Typescript](https://www.typescriptlang.org/) - Language - [Next.js](https://nextjs.org/) - Framework - [Prisma](https://www.prisma.io/) - ORM - [Tailwind](https://tailwindcss.com/) - CSS - [shadcn/ui](https://ui.shadcn.com/) - Component Library - [NextAuth.js](https://next-auth.js.org/) - Authentication - [react-email](https://react.email/) - Email Templates - [tRPC](https://trpc.io/) - API - [Node SignPDF](https://github.com/vbuch/node-signpdf) - Digital Signature - [React-PDF](https://github.com/wojtekmaj/react-pdf) - Viewing PDFs - [PDF-Lib](https://github.com/Hopding/pdf-lib) - PDF manipulation - [Stripe](https://stripe.com/) - Payments - [Vercel](https://vercel.com) - Hosting ## Local Development ### Requirements To run Documenso locally you need - Node.js - Postgres SQL Database - Docker (optional) ### Developer Quickstart > **Note**: This is a quickstart for developers. It assumes that you have both [docker](https://docs.docker.com/get-docker/) and [docker-compose](https://docs.docker.com/compose/) installed on your machine. Want to get up and running quickly? Follow these steps: 1. [Clone the repository](https://help.github.com/articles/cloning-a-repository/) it to your local device. ```sh git clone https://github.com/documenso/documenso ``` 2. Set up your `.env` file using the recommendations in the `.env.example` file. 3. Run `npm run dx` in the root directory - This will spin up a postgres database and inbucket mailserver in a docker container. 4. Run `npm run dev` in the root directory 5. Want it even faster? Just use ```sh npm run d ``` #### Access Points for Your Application 1. **App** - http://localhost:3000 2. **Incoming Mail Access** - http://localhost:9000 3. **Database Connection Details** - **Port**: 54320 - **Connection**: Use your favorite database client to connect using the provided port. ## Developer Setup ### Manual Setup Follow these steps to setup documenso on you local machine: 1. [Clone the repository](https://help.github.com/articles/cloning-a-repository/) it to your local device. ```sh git clone https://github.com/documenso/documenso ``` 2. Run `npm i` in root directory 3. Generate your `.env` from the `.env.example` 4. Set DATABASE_URL value in .env file - You can use the provided test database url (may be wiped at any point) - Or setup a local postgres sql instance (recommended) 5. Create the database scheme by running `db:migrate-dev` 6. Setup your mail provider - Set `SENDGRID_API_KEY` value in .env file - You need a SendGrid account, which you can create [here](https://signup.sendgrid.com/) - Documenso uses [Nodemailer](https://nodemailer.com/about/) so you can easily use your own SMTP server by setting the `SMTP` variables in your .env 7. Run `npm run dev` root directory to start 8. Register a new user at http://localhost:3000/signup --- - Optional: Seed the database using `npm run db:seed` to create a test user and document - Optional: Create your own signing certificate - To generate your own using these steps and a Linux Terminal or Windows Subsystem for Linux (WSL) see **[Create your own signing certificate](./SIGNING.md)**. ### Run in Gitpod - Click below to launch a ready-to-use Gitpod workspace in your browser. [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/#https://github.com/documenso/documenso) ## Docker > We are still working on the publishing of docker images, in the meantime you can follow the steps below to create a production ready docker image. Want to create a production ready docker image? Follow these steps: 1. cd into `docker` directory 2. Make `build.sh` executable by running `chmod +x build.sh` 3. Run `./build.sh` to start building the docker image. 4. Publish the image to your docker registry of choice (or) if you prefer running the image from local, run the below command ``` docker run -d --restart=unless-stopped -p 3000:3000 -v documenso:/app/data --name documenso documenso:latest ``` ## Self Hosting We support a variety of deployment methods, and are actively working on adding more. Stay tuned for updates! ### Railway [![Deploy on Railway](https://railway.app/button.svg)](https://railway.app/template/DjrRRX) ### Render [![Deploy to Render](https://render.com/images/deploy-to-render-button.svg)](https://render.com/deploy?repo=https://github.com/documenso/documenso) ## Troubleshooting ### I'm not receiving any emails when using the developer quickstart When using the developer quickstart an [Inbucket](https://inbucket.org/) server will be spun up in a docker container that will store all outgoing email locally for you to view. The Web UI can be found at http://localhost:9000 while the SMTP port will be on localhost:2500. ### Support IPv6 In case you are deploying to a cluster that uses only IPv6. You can use a custom command to pass a parameter to the Next.js start command For local docker run ```bash docker run -it documenso:latest npm run start -- -H :: ``` For k8s or docker-compose ```yaml containers: - name: documenso image: documenso:latest imagePullPolicy: IfNotPresent command: - npm args: - run - start - -- - -H - '::' ``` ## Repo Activity ![Repository Activity](https://repobeats.axiom.co/api/embed/622a2e9aa709696f7226304b5b7178a5741b3868.svg)