Self-Hosted vs SaaS: Why AuraBoot Gives You Both

The enterprise software world presents you with a binary choice: run software on your own infrastructure (self-hosted) or pay someone else to run it (SaaS). Each option has real trade-offs, and for years, you had to pick one. AuraBoot is designed so you don't have to.

The Self-Hosted Case

Organizations choose self-hosting for legitimate reasons:

• Data sovereignty: Regulated industries (healthcare, finance, government) may require data to stay within specific jurisdictions
• Security control: You manage the network, firewalls, encryption keys, and access policies
• Customization depth: Full access to the codebase means unlimited modification
• Cost at scale: After a certain number of users, self-hosting is cheaper than per-seat SaaS pricing
• Offline capability: Some environments have restricted or no internet access

The downside? You own the infrastructure. Updates, backups, monitoring, and scaling are your responsibility.

The SaaS Case

SaaS (Software as a Service) appeals for opposite reasons:

• Zero ops: No servers to manage, patch, or monitor
• Instant onboarding: Sign up and start using immediately
• Automatic updates: New features appear without upgrade projects
• Elastic scaling: Infrastructure grows with your usage
• Lower initial cost: Monthly subscription vs. upfront infrastructure investment

The downside? Your data lives on someone else's servers. You're subject to their pricing changes, feature roadmap, and availability.

Why Not Both?

AuraBoot's architecture makes dual deployment possible because of three design decisions:

1. Configuration as Code

Every business definition — models, fields, commands, pages, workflows — is expressed as JSON files in plugin directories. These files are identical whether you deploy on your laptop, your data center, or our cloud.

plugins/
  crm/
    config/
      models.json
      fields.json
      commands.json
      pages.json

There's no "cloud-only" feature locked behind a proprietary API. The DSL is the same everywhere.

2. Multi-Tenancy from Day One

AuraBoot's TenantLineInterceptor automatically scopes every database query to the current tenant. This means a single deployment can serve multiple organizations with complete data isolation.

For self-hosted deployments, this enables department-level isolation within a single installation. For SaaS, it enables serving thousands of tenants from shared infrastructure.

3. Entitlement-Based Feature Gating

Instead of shipping different binaries for different deployment models, AuraBoot uses an entitlement system to control feature access:

Free Tier  → 3 users, 5 models, community plugins
Pro Tier   → 25 users, unlimited models, all plugins
Max Tier   → Unlimited users, AI features, premium support

The same codebase runs everywhere. The entitlement layer determines what's available. Self-hosted users can use the Community edition under its source-available terms, or purchase a license key for commercial and enterprise features.

How It Works in Practice

Scenario: Growing Startup

1. Month 1: Deploy AuraBoot on a $20/month VPS. Set up CRM and project management for a 5-person team.
2. Month 6: Team grows to 20. Migrate to AuraBoot Cloud for managed hosting and automatic backups.
3. Month 18: Close a government contract requiring on-premise deployment. Export the entire configuration, import it into an air-gapped installation. Same app, different environment.

Scenario: Enterprise

1. Pilot: Evaluate on AuraBoot Cloud with a free tier. Build a proof of concept.
2. Procurement: Move to self-hosted in your Kubernetes cluster. Integrate with Active Directory and internal databases.
3. Multi-region: Deploy separate instances in EU and US data centers for data residency compliance, using the same plugin packages.

The Source-Available Foundation

AuraBoot Community is source-available under AuraBoot License Agreement v1.3. This means:

• You can always self-host the community edition at zero cost
• You can inspect, audit, and modify every line of code
• You're not locked into a vendor — your data and configuration are always portable
• Commercial editions add white-label rights, official support, paid plugin packages, and enterprise terms

This model aligns incentives: we succeed when the platform is good enough that you choose to pay for premium features, not because you're locked in.

Technical Architecture That Enables Both

The reason most platforms can't offer both deployment models is architectural coupling. SaaS platforms bake in assumptions about multi-tenancy, metering, and shared infrastructure. Self-hosted software assumes dedicated resources and local configuration.

AuraBoot avoids this with three architectural patterns:

Environment-Agnostic Configuration

All platform settings use Spring Boot's externalized configuration. The same application JAR runs everywhere — the environment determines behavior:

# Self-hosted: local PostgreSQL, file storage
auraboot:
  storage:
    type: local
    path: /data/uploads

# Cloud: managed PostgreSQL, S3 storage
auraboot:
  storage:
    type: s3
    bucket: auraboot-prod

Stateless Application Tier

AuraBoot's application servers are stateless. Sessions use JWT tokens, caches use Redis, and file storage is pluggable. This means you can run a single instance on a $20 VPS or auto-scale across a Kubernetes cluster — the application doesn't care.

Plugin Portability

Plugin packages (JSON configuration files) are environment-agnostic. A CRM plugin exported from a self-hosted instance imports identically into a cloud deployment. The plugin import command is idempotent and handles schema differences automatically.

Migration Between Models

Switching between self-hosted and SaaS shouldn't require a rewrite. With AuraBoot:

• Export: auraboot plugin export bundles your entire configuration
• Import: auraboot plugin import loads it into any AuraBoot instance
• Data migration: Standard PostgreSQL pg_dump and pg_restore
• Zero code changes: The same plugin package works on any deployment

What This Means for You

You don't need to predict your deployment needs three years from now. Start wherever makes sense — a laptop, a cloud VM, or our managed service — and change your mind later without losing work.

The question isn't "self-hosted or SaaS?" It's "what do I need today?" AuraBoot adapts to the answer, and adapts again when your answer changes tomorrow.

Talk to us about managed access or self-host in 5 minutes with Docker.