Choose the fastest correct path to invoicing in your product
Start free in sandbox, create an entity, generate the right key, and issue your first invoice before you think about go-live. Space Invoices is for teams that need embedded invoicing and compliance infrastructure, not just invoice CRUD.
When this is overkill vs exactly right
Overkill if you only invoice from one central business and do not need platform-style entity isolation.
Exactly right if your product needs one entity per customer or seller, embedded invoicing, and country-aware compliance.
Especially right if you expect country expansion, marketplace complexity, or payment-linked document flows later.
Still self-serve, but not only for startups
The docs and sandbox stay public because evaluation should stay fast. Larger buyers should still see a clear path to architecture discussions, rollout planning, and higher-touch support when they need it.
This product is shaped by production invoicing experience across 20M+ issued documents, which is why the expensive parts are modeled explicitly: entity isolation, country behavior, corrections, and rollout paths.
Talk to us about rolloutWhat you can build quickly vs what will slow you down
AI can help you build invoice CRUD, forms, PDFs, and SDK scaffolding. It does not take ownership of jurisdiction rules, fiscalization, tenant isolation, or production support when something goes wrong.
Invoice creation, templates, customer CRUD, and basic dashboard wiring.
Country rules, corrections, exports, access models, and multi-entity correctness in production.
Designed for entity-per-customer and entity-per-seller platforms
Use account keys when your backend is the platform control plane.
Create one entity per customer or seller to preserve numbering, branding, and country behavior.
Add entity-key or user-based access later if customers need direct document workflows.
Validate one sandbox flow before you design the whole live rollout.
Choose your integration path
Most teams should start with the JavaScript SDK. Use embed when speed matters more than UI ownership, React UI when you want copy-paste control, and direct API when your stack or workflow is already opinionated.
JavaScript SDK
Backend workflows, custom UI, full API control
Embed SDK
Fastest route to working invoicing UI
React UI
React teams that want copy-paste control
Direct API
Non-JS stacks or teams building their own client
What actually happens after signup
1. Create your account
Start in sandbox first if you want zero-risk testing and realistic docs exploration.
2. Create your first entity
New accounts create an entity after signup. That entity is the business context for documents, numbering, customers, items, and settings.
3. Generate the right key
Use account keys for multi-entity control and entity keys for one isolated business context.
4. Issue and inspect one invoice
Create, render, and optionally email one sandbox invoice before you design the full live rollout.
Start from the page that answers your next question
These are the pages most technical teams need before or immediately after signup.
Need the docs mapped to your product shape?
Start from the user story closest to your architecture, then drop into the matching guide.
SaaS Platforms
One entity per customer, with a clear access model.
Marketplaces
One entity per seller, unified control for the marketplace.
Fintechs
Payment events, reconciliation, and invoicing in one product flow.
E-Commerce
Turn orders and refunds into invoices and credit notes.
Accountants
Switch between client entities without losing isolation.
Start with one workflow, not a whole rewrite
Free sandbox with no time limit. Prove one entity and one invoice flow before deciding how much UI, compliance, and rollout surface you want to own.