Four services. One platform.
smbCloud is built around four core services: Deploy, Auth, Mail, and GresIQ. They are separate products, but they belong together. That is the point.
Ship apps
Deploy
Deploy NodeJS, Swift, and Ruby apps with one command. No YAML maze. No container busywork just to get something online.
- SSH-based deploys from the smb CLI
- NodeJS, Swift, and Ruby support out of the box
- Release history and rollback-friendly workflow
Accounts and access
Auth
Handle sign-in, signup, sessions, and hosted auth flows without bolting together three different vendors first.
- Console account signup and sign-in
- Hosted auth apps for end users
- User and access management across projects
Domain mail routing
Set up one Mail app per project, add inbox routes for the domain, keep forwarding on, and start keeping a real record of what came in.
- One Mail app per project
- Many inbox routes under one domain
- Forwarding plus stored inbound messages
Data layer
GresIQ
Run the database side of your product inside the same platform instead of scattering app logic, auth, and data across disconnected tools.
- Database-oriented service setup
- Connection and service management in one place
- Built to live alongside Deploy, Auth, and Mail
Why this matters
Most teams do not need more tools. They need fewer seams.
Deploy, Auth, Mail, and GresIQ solve different problems. Still, they are all part of the same application stack. smbCloud keeps them close, so you spend less time stitching products together and more time shipping.
A simple stack
- Deploy
- ship the app
- Auth
- handle accounts
- route domain email
- GresIQ
- run the data layer
Start with one service. Add the rest when you need them.
That is usually the better path anyway.
Create free account