What does security testing mean?

We examine the system the way an attacker would — sign-in, access, forms and software versions — and close whatever we find before anyone can use it. The essential plans use automated scans; the higher plans add manual reviews and audits.

What are the hours of changes for?

Small work: copy and images, a new page, a small fix or improvement. Work beyond the month’s hours is done at the studio’s hourly rate, and only after you approve it.

Yes. Before it starts you change it yourself in the project room; once it has started, a message to the studio changes it from the next period.

How do phone calls work?

By arrangement, so both sides spend the time on the fix rather than waiting on the line; the higher plans add a direct line and an emergency line.

Are prices fixed in toman?

Each plan is priced in dollars and the toman figure follows the day’s rate — the same rule as every other price at the studio.

Website and software support and maintenance

After launch, the flame stays lit.

Nothing at Mashaal ends on launch day. What we build is kept updated, backed up and watched — and if something breaks, you know in advance how fast you will hear back.

See the plans Message on Telegram

Coverage

In every plan

Maintenance
Bug fixes, compatibility with new browsers and devices, and keeping the code healthy.
Updates
Security patches and dependency versions, before age turns into a problem — each plan at its own pace.
Backups
Regular backups of data and files; on the higher plans off the server, with restore drills.
Monitoring
Availability, errors and speed, with an alert before you see a problem.
Security testing
We test the system the way an attacker would; it goes deeper and more often as the plan goes up.

under 30 minutes

A system where every hour of downtime has a direct cost: payments, trading, round-the-clock work

Request this plan

Each plan is priced in dollars and converted to toman at the day’s rate; a year is twelve months’ price.

Everything, side by side

Each row a piece of work, each column a plan; a dash means the plan does not include it.

What is done	EmberEssential care	FlameBusiness	AzarProfessional	ThunderCritical	PhoenixEnterprise priority
Response and reach
Response from the site and portalA request you make in the project room or on the site is answered within this time	2 business days	24 hours	under 6 hours	under 2 hours	under 30 minutes
Hours coveredWhen the support team works on requests, Tehran time	working days, 9:00–17:00	working days, 9:00–20:00	every day, 9:00–21:00	every day, 8:00–24:00	round the clock, every day
TelegramA Telegram message is answered within the hour on every plan	within the hour, in covered hours	within the hour, in covered hours	within the hour, in covered hours	within the hour, in covered hours	within 15 minutes, round the clock
PhoneCalls are arranged so both sides spend the time on the fix	by arrangement	by arrangement	by arrangement, the same day	a direct line in covered hours	a round-the-clock emergency line
A dedicated support leadOne person at the studio who knows your project and answers for it	—	—	—
Service back after an outage (target)Our target for bringing the service back, from the moment we know	2 business days	24 hours	8 hours	4 hours	1 hour
Technical care
Security updatesSecurity patches for the server, the framework and the plugins	monthly	every two weeks	weekly	weekly; urgent ones within 24 hours	continuous; urgent ones within 4 hours
Versions and dependenciesLibraries and software versions, before age turns into a problem	quarterly	monthly	monthly	every two weeks	weekly
Uptime monitoringThe site is checked from outside and every outage raises an alert	every 15 minutes	every 5 minutes	every minute	every minute, from several places	every 30 seconds, from several places
Error and speed monitoringServer errors and slow pages, before you see them	—	a monthly report	weekly, with alerts	daily, with instant alerts	live, with instant alerts
Speed tuningMeasuring and improving load and response times	—	yearly	quarterly	monthly	monthly, and whenever needed
Technical SEO healthThe sitemap, broken links, structured data and Google’s errors	—	a quarterly check	a monthly check	monthly, with the fixes	every two weeks, with the fixes
Domain, SSL and serverRenewals and server capacity, with nothing let slip	renewal reminders	renewals handled	fully managed	fully managed, with capacity planning	fully managed, capacity and scaling
Security and backups
BackupsOf data and files, so no failure costs you your work	weekly, kept 4 weeks	daily, kept 14 days	daily, 30 days, off the server	every 6 hours, 90 days, off the server	hourly, a year, in two places
Restore drillWe really restore a backup, so we know it works on a bad day	—	yearly	quarterly	monthly	monthly, with a disaster-recovery plan
Security and penetration testingWe test the system the way an attacker would	a monthly automated scan	an automated scan every two weeks	weekly scans, a monthly manual review	weekly scans, a manual review every two weeks	weekly scans and manual reviews, a quarterly audit
Incident reportAfter every outage: what happened, how it came back, what we changed so it does not recur
Changes and work
Hours of small changes a monthCopy, images, a new page or a small fix; more at the studio’s hourly rate, after your approval	1 hour	3 hours	8 hours	16 hours	32 hours
Support requests a monthThe requests you can make in the project room each month	3 requests	8 requests	15 requests	30 requests	unlimited
Unused hours carried overHours you do not use this month are not lost	—	—	to the next month	up to two months	up to three months
Priority in the studio’s queueWhen work arrives at once, which starts first	standard	standard	high	very high	first in line
Reports and partnership
Work reportsWhat was done, what we saw and what we suggest next	a quarterly summary	monthly	monthly, with a review call	every two weeks, with a call	weekly, and a monthly management report
Training for your teamUsing the panel and new features, for the people who work with the system every day	—	one session a year	quarterly	monthly	whenever needed
An improvement planThe improvements we prioritise together	—	—	quarterly	monthly	monthly, prioritised together

Response

Response times

Telegramwithin the houron every plan
Phoneby arrangementthe call time is agreed in advance
Site and portalby planeach plan’s time is below

When it breaks

When something breaks

01
Detect
A monitoring alert or your message — whichever comes first.
02
Respond
You hear back within your plan’s time and know who is on it.
03
Restore
Service comes back first; then the cause is found and closed.
04
Report
A short account of what happened and what we changed so it does not recur.

Questions

Every plan includes maintenance, updates, backups, monitoring and security testing. They differ in how fast requests are answered, the hours covered, how often and how deeply that work is done, the hours of changes each month and how closely we work together — the comparison shows it all side by side. Telegram is answered within the hour on every plan.

Begin

Have a system that has to stay up?

Choose a plan or ask on Telegram; the answer comes within the hour.

Request support Message on Telegram

Maintenance

Updates

Backups

Monitoring

Security testing

Ember

Flame

Azar

Thunder

Phoenix

Everything, side by side

Detect

Respond

Restore

Report

01How do the plans differ?

02What does security testing mean?

03What are the hours of changes for?

04Can I change plans?

05How do phone calls work?

06Are prices fixed in toman?

Have a system that has to stay up?