Platform
Multi-tenant security, isolation and infrastructure
Every shop’s data is isolated at the query layer, authenticated with JWT, protected by rate limiting and served entirely over HTTPS, running on Redis, Horizon queues and Octane. Granular roles and an audit trail sit on top, so access control and infrastructure are one system, not two.
yourstore.com
Security posture
- JWT authenticationOn
- Rate limitingOn
- Tenant isolationPer shop
How it works
How it works
- 1
Isolate per shop
Every database query is scoped to the requesting shop.
- 2
Authenticate with JWT
Sessions and API access run on JWT tokens.
- 3
Limit and encrypt
Rate limiting and HTTPS apply to every endpoint.
- 4
Run on solid infrastructure
Redis, Horizon queues and Octane keep it fast under load.
Configuration
What you can configure
| Setting | What it does |
|---|---|
| Tenant isolation | Per-shop data isolation enforced at the query layer. |
| Authentication | JWT for session and API access. |
| Rate limiting & HTTPS | Enforced across every endpoint. |
| Infrastructure | Redis for caching and sessions, Horizon queues, Octane for throughput. |
FAQ
Frequently asked questions
Can one shop see another shop’s orders?
No, every query is scoped to the requesting shop and tenant isolation is enforced at the query layer.
What protects the API from abuse?
Rate limiting on every endpoint, alongside JWT authentication and HTTPS throughout.
What runs the background jobs like bulk import?
Horizon queues, backed by Redis, with Octane keeping the application server fast under load.
Put this to work in your store today
Get started and turn this on for your store in minutes.
No card required · Live in a day · Support in Arabic and English