General

What is Rustume?

Rustume is a privacy-first resume builder: a SolidJS web app backed by a Rust API. Use it locally, self-host it, or sign in to the operated Rustume Cloud service for ready-to-use synchronization.

Read more in the docs →

Self-hosting

Do I need hosted Rustume Cloud to store my resumes?

No. Browser-local Rustume stores resumes on your device without an account, and a self-hosted connected deployment can provide account-backed storage and sync. Hosted Cloud removes the deployment and operations work.

Read more in the docs →

Can I run the connected features myself?

Yes. Configure Cloud mode with your own PostgreSQL database, WorkOS credentials, and deployment controls. Self-hosted connected Rustume supports the same product capabilities as the hosted service.

Read more in the docs →

Can self-hosted Rustume provide version history?

Yes, when you run a connected deployment. Browser-only storage is intentionally local, while connected mode provides synchronized storage and version restoration on infrastructure you operate.

Read more in the docs →

What do I operate when I self-host connected mode?

You operate identity configuration, storage, backups, monitoring, upgrades, and availability. Rustume Cloud exists for users who prefer those responsibilities already handled.

Read more in the docs →

Rustume Cloud

Can I sign up for hosted Rustume Cloud?

Yes. Hosted Rustume Cloud is the ready-to-use deployment: sign in, create or import resumes, and synchronize them across devices without configuring server infrastructure.

Read more in the docs →

Can I move local resumes into Rustume Cloud?

Yes. After signing in, import local resumes into account-backed storage. Local copies remain on the device, and the stored versions can participate in sync and history.

Read more in the docs →

Does paying for Cloud unlock additional Rustume features?

No. Hosted access pays for a deployed and operated service. The open-source connected application may provide the same storage, sync, sharing, history, and API capabilities when you host it yourself.

Read more in the docs →

Does Rustume Cloud work offline?

Connected Rustume supports offline work with queued synchronization when a device reconnects, including conflict handling for diverged edits.

Read more in the docs →

How do public resume pages work?

Publishing is opt-in. Connected deployments let you publish a selected read-only resume, add password protection when appropriate, and unpublish it again.

Read more in the docs →

Hosting and billing

What am I paying for with hosted Rustume Cloud?

You pay for an already deployed application and operated synchronization service, including storage operations, backups, monitoring, and updates. Product capabilities are not reserved for subscribers.

Read more in the docs →

What happens if I stop hosted access?

Hosted access and its data-retention terms apply to the operated service. Export portable data before ending access when needed; the open-source application remains available for self-hosting.

Read more in the docs →

Why does Rustume Cloud use Paddle for payments?

Paddle acts as Merchant of Record for hosted-service payment, invoicing, and tax handling. Billing grants use of operated hosting, not exclusive application features.

Read more in the docs →

Privacy and encryption

What personal data does Rustume Cloud store?

Rustume links accounts with an opaque WorkOS identifier rather than copying profile fields into its account record. Resume documents can contain personal data and must be protected accordingly.

Read more in the docs →

What is end-to-end encryption?

Optional end-to-end encryption encrypts a resume in the browser using user-held secret material before storage, limiting what the hosting operator can read without user participation.

Read more in the docs →

Is encryption available to self-hosted connected deployments?

Yes. Encryption is a connected Rustume capability, not a paid-only hosted option. Self-hosted operators remain responsible for keys, database access, backups, and telemetry configuration.

Read more in the docs →

Why is Rustume licensed under AGPL-3.0?

AGPL keeps Rustume Cloud transparent: self-hosting and local CLI use are unrestricted, but offering Rustume as a network service requires sharing modifications under the same license. Template designs adapted from Reactive Resume remain MIT-attributed in THIRD_PARTY_NOTICES.

Read more in the docs →

Data and import

Which resume formats can I import?

JSON Resume, LinkedIn export ZIP, Reactive Resume (rrv3), and native Rustume JSON. The parser normalizes all formats into Rustume's unified schema.

Read more in the docs →

Why do the docs say Reactive Resume instead of rrv3?

Reactive Resume is the user-facing product name. rrv3 is the format identifier used in code and API tables when referring to the import format.

Read more in the docs →

What can API keys do?

Scoped API keys authorize programmatic connected workflows such as resume operations and rendering without sharing a browser session. They are available in hosted and self-hosted connected deployments.

Read more in the docs →

Still stuck?

Browse the full documentation, open a GitHub issue, or see Getting started with Cloud to begin using hosted Cloud or configure connected mode yourself.