Cloud
Cloud
Your studio's system runs
on a Cloud we look after
Everything from the domain and HTTPS to the database, scheduled jobs and backups. Your studio doesn't need its own servers or IT team.
- Domain and HTTPS The studio's single way in
- Apps and scheduled jobs Member app, back office and timed jobs
- Database and backups All of the studio's data
How one booking travels
It takes just a few seconds from a member tapping Book in a LINE chat to the instructor getting a notification and the back office seeing the booking.
- A member taps Book in LINE, and the request travels over HTTPS to the studio's domain.
- The member's identity is checked with LINE.
- The app on Cloud checks the booking rules.
- The booking is saved and a session is deducted in the database.
- The instructor is notified in LINE.
- The new booking shows up in the back office.
Working for your team, 24 hours a day
Cloud now handles the jobs that used to need someone on hand, each at its set time, from class reminders and moving up the waitlist to checking pending payments. Pick an hour on the dial to see what runs then.
Slide to see one hour at a time
08:00 – 08:59
08:00 Remind members of today's afternoon and evening classes
- Move up the waitlist when a spot opens60 runsEvery minute
- Check pending payments12 runsEvery 5 minutes
- Send scheduled messages12 runsEvery 5 minutes
- Mark no-shows 30 minutes after the start time6 runsEvery 10 minutes
- Send after-class summaries and ask for reviews4 runsEvery 15 minutes
- Back up the database1 run10 past every hour
- 12 jobs
- Scheduled jobs, set to Thailand time
- 2,286 runs
- Checks and jobs Cloud runs for you in a day
- No overlap
- A job that hasn't finished won't be started again on top of its last run.
Every request has to pass the checks first
Anything coming into Cloud, whether from members, LINE or a payment provider, has to prove it came from the real source before the system acts on it. Try sending a few different requests.
Choose a request to send to Cloud
- HTTPS
- Every page and every request between the user's device and Cloud
- SHA-256
- The HMAC signature that verifies messages from LINE and payment results
- bcrypt
- Passwords are stored as hashes, so no one can read the real password.
- 0
- Customer card numbers that pass through the server
A separate system for each studio
Each studio has its own system and database. Member and sales data aren't mixed with any other studio's.
Keys stay out of the code
Connection keys for LINE, the payment provider and email are kept as server settings, and are automatically stripped from the activity log.
Ask the source before adding sessions
The system confirms the payment status with the provider before adding sessions, and rechecks pending payments every 5 minutes.
Go back to any hour from the last 7 days
Cloud backs up the whole database every hour. If data is deleted or changed by mistake, it can be restored from an earlier hour's file. Each square below is one backup file.
Selected file
—
The latest file, backed up less than an hour ago. If you need to restore, at most an hour of data could be lost.
Files older than 7 days
are deleted automatically.
- 1 hour
- A full backup every hour
- 168 files
- Kept for about 7 days
- .sql.gz
- A standard format that opens in regular MySQL
Who looks after what
We look after everything on Cloud. The studio looks after only a few things, and most of them are done once, when you get started.
Svana looks after
- All servers and Cloud
- HTTPS certificates and renewals
- System updates and bug fixes
- All 12 scheduled jobs
- Hourly database backups
- Restoring data when the studio asks
The studio looks after
- The domain, and pointing it at Cloud the first time
- The studio's LINE Official Account
- The merchant account with the payment provider
- Staff accounts and each person's role
- Passwords, and the email that receives back-office sign-in codes