Skip to content

SaaS

The SaaS version is the fastest way to get started — no infrastructure to manage, sign up and start writing prompts in under a minute.

Key characteristics

Detail
IdentityClerk (email/password, Google, GitHub, SSO on enterprise plans)
Data planeDynamoDB, AWS-hosted
Cache layerRedis (graceful degradation if unavailable)
AI featuresPrompt optimization via Azure OpenAI
EmailSMTP for org invites
SLAPer agreement; standard tier is best-effort
RegionUS-East default; ask about multi-region

Authentication model

The SaaS authorization model is simpler than on-prem:

  1. The API key is validated.
  2. The key is checked for user_id.
  3. The project's organization is loaded, but not matched against the key — the project itself enforces org-scoped access.

If you're on the SaaS build, you don't need to think about the multi-org membership model described in on-prem(. Each key just works against the projects you have access to.

See Authentication( for the full model.

Install the SaaS SDK

bash
pip install --extra-index-url https://elsai-core-package.optisolbusiness.com/root/elsai-prompts-sass/ elsai-prompts==2.0.0

The SaaS build of the SDK hardcodes the hosted URL — you don't need to set base_url.

python
from elsai_prompts.prompt_manager import PromptManager

pm = PromptManager(
    api_key="YOUR_KEY",
    project_id="YOUR_PROJECT_ID",
    environment="development",
)

When to choose SaaS

You want to start in minutes

No infrastructure setup, no deployment. Sign up, create a project, write a prompt.

No data-residency requirements

SaaS runs on AWS US-East by default. If you need EU residency or strict data-locality, talk to us — or use on-prem.

Managed upgrades

We upgrade the platform without you doing anything. New features land automatically.

Smaller teams

For teams under ~50 active prompt authors, SaaS is the right default.

When to consider on-prem instead

  • Regulatory or contractual data-residency requirements
  • Air-gapped or restricted-network environments
  • Compliance posture that mandates self-host (SOC2 Type II + specific controls)
  • Volume / latency SLAs that benefit from in-VPC deployment

See On-Prem(.

Migrating between SaaS and on-prem

The SDK API is identical between the two. Migration is:

  1. Re-create your projects and prompts on the target platform (or use the export/import tooling if available — ask support).
  2. Update your application's .env:
    • SaaS → on-prem: add PROMPT_MANAGER_API_URL=https://prompts.your-company.com.
    • On-prem → SaaS: remove that env var.
  3. Reinstall the SDK from the appropriate index URL.

No application code changes.

Limits and quotas

ResourceDefault
Organizations per account5
Projects per organization50
Prompts per project500
Versions per promptunlimited
API key fetchesrate-limited per key

Support

Copyright © 2026 elsai foundry.