IpInkpacket

Multi-tenant e-signature

Agreements that close in one sitting.

Inkpacket is a workspace for sending PDFs out for signature. Upload, place fields, share a link, download the signed file. Built for operators who need tenants, not a personal inbox tool.

inkpacket.com

Envelope

Master services agreement

A. Hale

  • StatusCompleted
  • Signeralex@northfield.co
  • Audit events6

Fields on the page

Drop signature, date, and text fields onto a PDF. The signer fills the same places you marked.

One link to finish

Send a signing URL. No account required for the signer. You get the completed file back.

Audit that is readable

Created, sent, viewed, signed, completed, downloaded — stored on the document, scoped to the org.

Workspaces, not a pile

Owner, admin, and member roles. Invite a seat. Every envelope stays inside its organization.

Pricing that matches how you send

Proposal copy. Stripe is optional until you turn it on.

Starter

For a small team sending agreements every week.

$29

per month

  • 20 envelopes / month
  • 3 seats
  • Org-scoped audit log

Growth

For operators who live in the desk all day.

$79

per month

  • 100 envelopes / month
  • 10 seats
  • Org-scoped audit log

Agency

For agencies running many client workspaces.

$199

per month

  • 500 envelopes / month
  • 50 seats
  • Org-scoped audit log

Questions we hear first

Is Inkpacket original software?

Yes. Inkpacket is written in Next.js and Prisma, with our own envelope, field, and audit models. It is not a re-skin of someone else's signing product.

Can more than one company share an install?

Yes. Every document, signer, invite, and audit event is scoped to an organization. Members of workspace A cannot read workspace B.

What happens if we do not have Stripe or Resend keys yet?

The product still runs. Billing routes return a stub response, and outbound email is logged instead of sent. You can copy the signing link from the desk.

Where are PDFs stored?

Behind an S3-compatible storage interface. In development, files land on the local filesystem. In production, point S3_* at your bucket.

Read the rest