Your domain
Sign-in and the editor live at your-slug.resumeblox.com, with your wordmark,
primary color, and copyright in the footer.
Enterprise
Resume Blox on your domain, behind your SSO.
A dedicated tenant for your organization. Your subdomain, your identity provider, your brand on exported PDFs, and a database that no other tenant can touch. We provision the moving parts so your team can ship resumes the same day.
Talk to us or write to [email protected]
What you get
Six pieces, one tenant.
Your SSO
SAML or OIDC against your identity provider, set up through Clerk Organizations. No second password for your team to manage.
Isolated data
Every tenant gets its own database and key-value store. No shared tables, no shared queries, no chance of a missed tenant filter leaking data sideways.
Branded PDFs
Exports carry your accent color and an optional footer logo. The same eight resume themes you already get, tinted to match your brand.
Import existing resumes
A consultant arrives with a PDF. Drop it into the editor and we extract the blocks (contact, experience, education, skills) into editable fields. Two minutes later it ships back to a client in your brand, no retyping.
Career Analysis and coaching credits
Every plan bundles credits for the paid consumer products: Career Analysis Reviews (deep-dives on a target role and geography) and coaching sessions. Credit counts scale with the tier you pick, so the bundle sizes to your team without anyone having to manage individual subscriptions.
How it works
Three steps. Usually one business day.
- 01
You send branding and an IT contact
Slug (the subdomain you want), display name, primary and accent colors, a logo file under 50KB, and the person on your side who owns SSO. That is the whole intake.
- 02
We exchange SSO metadata
We create a Clerk Organization for you with a SAML or OIDC connection. We hand you the ACS URL and Entity ID. Your IdP admin configures their side and sends the metadata back. We paste it in. Done.
- 03
We provision and verify
A single command spins up your Worker, database, KV store, mail subdomain, and custom domain. We run the smoke checks (login, resume create, PDF export, tenant-config endpoint) and hand you the keys.
Pictured: a staffing firm
Cascade Talent. Their brand, in our editor.
A fictional staffing firm running on Resume Blox. Their recruiters and consultants build resumes inside the editor, and every page that ships to a client carries Cascade's brand. Your tenant looks like this with your wordmark, your accent color, and your domain in place of theirs.
Cascade Talent
Candidates Submissions
Single sign-on
Sign in to Cascade Talent.
Use your Cascade work account. No second password, no separate invite list.
Provisioned by Resume Blox Enterprise.
The header strip, the call to action, and the brand mark in the nav are the three places Cascade's color shows up. The PDFs their consultants export carry the same accent, like so.
Branded resumes
Every candidate ships in your brand.
Below is a candidate Cascade is submitting to a client. Accent strip across the top, section headings in Cascade's color, a "Submitted by" line at the top, and a small Cascade mark in the footer. To the client, the page reads as Cascade's first and the candidate's second.
Submitted by Cascade Talent · Reference CT-2026-0418
Summary
Platform engineer with a decade of experience scaling production services and mentoring teams. Available for contract or contract-to-hire engagements, remote first, US time zones.
Experience
Senior Software Engineer 2022 to now
Northwind Technologies
- Led the migration off a legacy monolith into four production services without missing a quarterly ship.
- Cut median read latency in half by introducing a tiered cache layer in front of the inventory API.
- Mentored four engineers across two promotion cycles.
Software Engineer 2019 to 2022
Aperture Robotics
- Owned the simulation pipeline that powered weekly customer demos.
- Shipped the first internal SDK used by every robot in the warehouse fleet.
Selected skills
TypeScript, Rust, Postgres, distributed systems, Kubernetes, Terraform, technical
mentorship, cross-team release coordination
Theme pictured is one of the eight that ship by default. Each one accepts your accent color, your "submitted by" line, and your footer mark, so the candidate's resume always reads as yours first.
How we keep tenants apart
Isolation is a deploy property, not a query convention.
Each tenant gets a separate Cloudflare D1 database, a separate KV namespace, and a separate Worker deployment. There is no shared schema with a tenant_id column for someone to forget. Frontend code ships to all tenants at the same time. Worker code, secrets, and data do not.
- Dedicated D1 database per tenant, bound to the tenant's Worker at deploy time.
- SSO-only sign-in, scoped by Clerk Organization membership.
- Per-tenant Resend mail subdomain (
mail.your-slug.resumeblox.com), so coaching emails ship from your name, not ours. - Decommissioning is a single command that detaches DNS, deletes the Worker, KV, and database, and removes the tenant from the build manifest.
Ready to talk?
Send a note with your team size, identity provider, and any timing constraints. We will reply with next steps and a number the same day.
Email [email protected]A few clarifications
What does it cost?
Custom. The price scales with seat count, SSO complexity, and whether you need invoice billing or a self-serve Stripe flow. Send a note and we will send a number, usually the same day.
Do you support SCIM provisioning?
Not on the standard package today. Clerk supports SCIM and we have run it for one tenant on request. If automated user provisioning is a hard requirement, flag it in your email and we will scope it in.
Can the same user belong to more than one tenant?
Yes. A Clerk user can be a member of multiple organizations. Inside the app, the active tenant is pinned by the subdomain they signed in at, so there is no risk of seeing the wrong organization's resumes.
How long does setup take?
Once your IT contact has the SSO metadata ready and DNS records are in place, the automated provisioning runs in about five minutes. Most of the wall-clock time is waiting on DNS propagation and SSO configuration on your end. A same-day cutover is normal.
Can we self-host?
No. We host and operate every tenant. There is no self-hosted distribution.
What happens to our data if we leave?
Decommissioning detaches your subdomain, deletes the Worker and KV, and on request deletes the database (D1 time-travel snapshots remain for 30 days for safety). Before deletion we can export a full data dump in a format you specify.