One library. Six databases.
Rogiant ships with adapters for the most popular databases so your Roblox tooling can cache aggressively, persist forever, and scale from a hobby script to a production service — without changing your application code.
Why pair Rogiant with a database?
The Roblox API is rate-limited and lossy by design. Storing what you fetch lets you build dashboards, alerting, and analytics that the platform doesn't provide natively.
Cache repeated lookups
Store usernames, item details, thumbnails, and metadata to reduce Roblox API requests and avoid 429 errors.
Preserve history
Save reseller floors, trade counts, user sales, and role states over time so you can query trends.
Build resilient automation
Persist cursors, processed IDs, and checkpoints so long-running jobs can resume after a crash.
Serve fast UIs
Render dashboards directly from your database, then refresh from Roblox in the background.
Choose your adapter
Pick the database that fits your workload. The Rogiant SessionDatabase API stays the same across all of them.
SQLite
Zero-config local persistence — perfect for bots, scripts, and dev.
INSTALL
pip install rogiant- Bundled by default — no extra deps
- File-based, single-process
- Great for caching and offline jobs
One API across every backend
Every adapter implements the same SessionDatabase interface. Start on SQLite, graduate to Postgres, and keep your code identical.
Adapter comparison
| Feature | SQLite | PostgreSQL | MySQL | MongoDB | Redis | Supabase |
|---|---|---|---|---|---|---|
| Setup difficulty | Trivial | Moderate | Moderate | Easy | Easy | Easy |
| Best for | Local + bots | Production | Shared hosting | Flexible schemas | Caching / queues | Hosted Postgres |
| Concurrent writers | Limited | Excellent | Excellent | Excellent | Excellent | Excellent |
| Async support | Yes | Yes | Yes | Yes | Yes | Yes |
| TTL / eviction | Manual | Manual | Manual | Indexed | Native | Manual |