---
title: Deploy DocuSeal with AI on Blossom
url: "/deploy/docuseal/"
canonical_url: https://docs.blossom88.com/deploy/docuseal/
markdown_url: https://docs.blossom88.com/deploy/docuseal.md
summary: Deploy DocuSeal with AI on Blossom. Collect document signatures with managed
  PostgreSQL, Redis, and private S3-compatible file storage.
categories:
- deployment
- productivity
---

# Deploy DocuSeal with AI on Blossom

[DocuSeal](https://www.docuseal.com/) turns PDFs into signing forms. Upload a
document, place the fields, and send a link for someone to complete and sign.

It uses Ruby on Rails with a Vue-based form builder. PostgreSQL stores the
records and Redis holds background work. Browse the
[source on GitHub](https://github.com/docusealco/docuseal).

This setup runs on regular App Capacity with managed PostgreSQL and Redis.
Documents live in your private S3-compatible bucket, such as Cloudflare R2.

[Install the Blossom CLI and skill](/learn/getting-started/install/)
on your agent's machine and choose a Blossom Cloud Location when you log in.
You can also use
[Blossom BYOC (bring your own cloud)](/learn/getting-started/choose-your-cloud/#blossom-byoc).

## Ask Your Agent

> **Ask your AI agent:** Deploy DocuSeal on Blossom with managed Postgres, Redis, and R2 for documents. Help me send a document for signing.

> Follow this guide: https://docs.blossom88.com/deploy/docuseal/



Your agent checks the current
[deployment requirements](https://www.docuseal.com/install), chooses a
maintained release, and saves the configuration. Supply bucket and SMTP
credentials through a private file.

| Part | Purpose |
|---|---|
| DocuSeal Service | Document builder, signing pages, and background worker |
| Managed PostgreSQL | Accounts, templates, signing records, and encrypted settings |
| Managed Redis | Background jobs |
| Your private S3-compatible bucket | Original and completed documents |
| Your SMTP provider | Signing invitations and notifications |

Keep administration behind **Blossom Account access** and native DocuSeal
sign-in. Allow the recipient signing pages and their required assets and file
routes through Blossom's access policy. Check a signing link in a separate
browser without a Blossom session; keep the bucket private.

## Send a Sample Document

> **Ask your AI agent:** Help me upload a sample PDF, add name and signature fields, and test the signing link.

> Follow this guide: https://docs.blossom88.com/deploy/docuseal/



Use a document without confidential information and a recipient address you
control. Complete the form in a separate browser, then download the signed PDF
and check the signing record in the dashboard.

![DocuSeal's PDF form builder with name, signature, and date fields.](/assets/images/guides/docuseal/editor.png)

Use a verified SMTP sender for real invitations. Our deployment test used an
internal mail catcher to check invitation generation and receipt; it did not
qualify inbox deliverability.

<details class="optional-reading" markdown="1">
<summary>Commands behind the deployment</summary>

Create a prebuilt-image Environment, then create and link PostgreSQL and Redis:

    blossom app:create --data app.yml
    blossom environment:create --data environment.yml
    blossom database_instance:create --data postgres.yml --follow
    blossom cache_instance:create --data redis.yml --follow
    blossom environment_link:create --data database-link.yml
    blossom environment_link:create --data redis-link.yml
    blossom env_var:push --environment environment-100 --file .env.production
    blossom service:create --data docuseal-service.yml
    blossom environment:deploy --id environment-100 --follow

Use the linked database and external Redis connection. Preserve
`SECRET_KEY_BASE` and `ENCRYPTION_SECRET` across updates; encrypted settings,
including the signing certificate, must remain readable.

Run database migrations once in a **Release Phase Hook** and disable automatic
migrations in the web process. Start the selected image's Puma application
explicitly when overriding its entrypoint, and use a health probe supported by
the image's Ruby runtime.

Configure the selected release's S3 storage endpoint, bucket, region, and
bucket-scoped credentials. With R2 and AWS SDK versions that add optional
checksums, set `AWS_REQUEST_CHECKSUM_CALCULATION=when_required` to avoid a
conflict with Active Storage's required checksum. Keep required checksums;
verify an upload and download through DocuSeal itself.

Set `SMTP_FROM` as well as the SMTP connection settings. Complete initial owner
setup privately and verify the public application URL used in invitations.

For a stop-before-start update, wait for each command to finish:

    blossom service:scale --id service-100 --desired-size 0 --follow
    blossom environment:deploy --id environment-100 --follow
    blossom service:scale --id service-100 --desired-size 1 --follow

</details>

## Keep Documents Through Updates

> **Ask your AI agent:** Update DocuSeal and check that my templates, completed signatures, and downloadable documents remain.

> Follow this guide: https://docs.blossom88.com/deploy/docuseal/



Keep one active application and embedded worker for this setup. Stop it before
starting a replacement, preserving PostgreSQL, Redis, the bucket, and application
secrets. This update path has a short outage. External storage alone does not
establish multi-Container support.

After updating, sign in again, open a completed submission, and download its
PDF. Send a new test invitation to check that the replacement can still process
background work.

## What You Get

- A private document dashboard and PDF form builder
- Signing links recipients can open without a Blossom account
- Templates and signing records in managed PostgreSQL
- Original and completed documents in your private bucket
