FAQ
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.
Does this include notary, KBA, or qualified electronic signatures?
Not in this foundation. Those stay out of scope so the desk can stay simple: PDF, fields, link, signature, audit, download.
What is the product domain?
inkpacket.com. From lines and public links should use that host in production.