You Own Your App

If you're building something serious — a commercial product, a tool your business depends on — these are exactly the right questions to ask before you commit to any platform. Here are clear answers.

1. Source code & ownership

• Export the full source code? Yes — as a downloadable zip or a GitHub repository invite, whichever you prefer. (See Getting Your Source Code.)
• Deployable outside LlamaPress? Yes. It's a normal Rails app; it runs on any standard Rails host — your own server, AWS, Azure, DigitalOcean, etc.
• Anything that stays dependent on us? Your application is standalone. What stays on our side is the Leonardo AI builder (the agent that writes and edits your app for you), our managed runtime, and platform tooling — that's LlamaPress technology and isn't part of the export. In practice: your live app keeps running on its own; you'd just lose the in-platform AI co-builder unless you keep a subscription or plug in your own AI keys.
• Self-host on your own infrastructure? Yes — Rails + PostgreSQL deploys anywhere. We're glad to help with the export and handoff.

2. Database & data portability

• Database technology: PostgreSQL (the app framework is Ruby on Rails).
• Export the complete database? Yes — a full PostgreSQL dump (pg_dump) of everything.
• Exports for your own safekeeping? Absolutely; we'll provide a full dump on request, and once you self-host you control it directly.
• Automated/scheduled exports? We run automated backups today, and we can set up a recurring export to your own storage — just ask.

3. Subscription & cancellation

• What stops if you cancel: the hosted version of your app and the in-platform AI builder. Anything you've already exported keeps working.
• Does your app stay accessible? On our hosting, while your subscription is active. If you've exported and self-hosted, it stays online under your control indefinitely.
• Reports, dashboards, auth: these are part of your app, so they keep working wherever it's hosted. AI-powered features need an LLM key (ours while subscribed, yours if self-hosted).
• Data retention after cancellation: per our Terms, we retain your data and backups for a reasonable period before deletion. We always recommend taking your own export before cancelling.

4. Backup & disaster recovery

• Frequency: automated backups to cloud storage (Amazon S3) on a configurable per-app interval, plus a backup whenever an app is paused. Active paid apps can be backed up daily or more often.
• Geographic redundancy: today backups live in a single region; we don't yet do cross-region replication. (Happy to discuss geo-redundancy for a dedicated setup.)
• Retention / RTO / RPO: on standard plans these are best-effort rather than a contractual SLA — your recovery point is bounded by the backup interval, and restores are typically completed the same day. For a commercial product we're glad to put a formal RTO/RPO and retention commitment in writing as part of a dedicated plan.
• Backup exports on request: yes.

5. Security & business continuity

• Continuity: managed infrastructure with automated backups — and your strongest protection is the export/self-host right itself.
• Prolonged outage: we restore from backups; and because you can hold your own source + database export, you're never solely dependent on us being up.
• Documented exit strategy: yes, and it's simple — export your source (GitHub/zip) + a full pg_dump, then deploy on your own infrastructure. We'll assist with the migration.

6. Scaling & best practice

• Limits (users, records, DB size, storage, AI usage) scale with your plan and instance size (CPU/RAM/storage). AI usage is governed by your plan's message allowance. We can scale your instance up or move you to a dedicated server as you grow.
• For a commercial SaaS that may eventually run independently: keep regular source + database exports (we can automate this), run on your own custom domain, and plan a dedicated/self-host path as you scale.