417 Solutions

Managed hosting for business-critical applications.

Typical managed hosting infrastructure fees with 417 Solutions are shown below. These service levels are designed for medium- to large-sized businesses that depend on their web applications. Pricing and service scope vary with your application, infrastructure requirements, and any external services involved.

At a glance

Typical monthly fees.

  • $250 — Shared Production
  • $450 — Dedicated Production
  • $575 — Protected Production
  • $995 — High Availability
Find your fit

What does your business need to recover?

Click the recovery targets that fit your business. We’ll highlight the lowest-priced plan that meets all your selections.

How much recent data could you afford to lose?

Recovery Point Objective (RPO) · Maximum recent data loss.

Hourly external backups support a 1-hour data recovery target.

How quickly should service be restored?

Recovery Time Objective (RTO) · Target time to restore service.

Protected and High Availability publish a 4-hour restoration target. Support response coverage is selected below.

Your recommended plan is Protected Production ($575/month estimated), based on all your selections.

See recommended plan ↓
Production plans

Protection that scales with business impact.

The right plan depends on two questions: how much recent data could the business afford to lose, and how quickly does production need to be restored after a serious infrastructure incident?

Shared Production

Your DEV/UAT and production environments share one server dedicated to your organization. Daily backups provide recovery protection.

$250
/ month
RPO Up to 24 hours
Response 6 business hours
RTO 8 business hours target
Mgmt. time 1 hour / month
  • Managed production environment
  • Daily protected backups
  • Basic external uptime monitoring
  • Routine security and platform maintenance
  • Business-hours infrastructure support
Compare plan View infrastructure ↓

Dedicated Production

Production is isolated from development and testing activity for stronger operational separation.

$450
/ month
RPO Up to 24 hours
Response 4 business hours
RTO 4 business hours target
Mgmt. time 1 hour / month
  • Dedicated production environment
  • Daily protected backups
  • Resource and uptime monitoring
  • Managed security and platform maintenance
  • Business-hours infrastructure support
Compare plan View infrastructure ↓

High Availability

Two active production servers run the same application simultaneously, sharing live traffic through a node balancer.

$995
/ month
Database RPO 10 minutes target*
Response 2 hours, 24/7
RTO 4 hours target*
Mgmt. time 3 hours / month
  • Two active servers running the same application
  • Automatic traffic distribution and health checks
  • Active/passive databases; standby takes over on failure
  • 24/7 automated critical availability monitoring
  • 24/7 response coverage for Severity 1 outages
Compare plan View infrastructure ↓
Side-by-side comparison

What changes as the plans move up.

Higher tiers improve isolation, recovery precision, monitoring, failover capability, support response, and the amount of infrastructure-management time included each month.

Service level Shared Dedicated Protected Recommended High Availability
Monthly price $250 $450 $575 $995
Production isolation Managed production environment Dedicated production environment Dedicated application + protected data tier Redundant production environment
Recovery Point Objective Up to 24 hours (once a day backups) Up to 24 hours (once a day backups) 1-hour backup recovery target 10-minute database PITR target*; 1-hour external backup target
Backup retention 7 days 14 days Hourly for 48 hours; daily through 30 days Hourly for 48 hours; daily through 30 days; weekly through 90 days
Recovery Time Objective 8 business hours target 4 business hours target 4 hours target 4 hours target; automatic failover may restore service sooner*
Critical response 6 business hours 4 business hours 2 business hours 2 hours, 24/7
Monitoring Basic uptime Uptime + resource monitoring Expanded monitoring + logging 24/7 availability + failover monitoring
Failover capability — — Data-tier protection Two active application servers + active/passive database failover
Included management 1 hour/month 1 hour/month 2 hours/month 3 hours/month
Support window Business hours Business hours Business hours + continuous monitoring 24/7 for Severity 1 outages

Older backups are retained at reduced frequency. Historical restores are limited to available recovery points. The 10-minute database RPO target applies to managed MySQL point-in-time recovery with available backups and transaction logs. Recovery from external backups has a separate 1-hour RPO target.

Inside each plan

See how your systems fit together.

Each server is a separate running system. With High Availability, both production servers actively serve the same application at the same time.

Shared Production

One server hosts this client’s DEV/UAT and production environments, including their applications and databases. The server is not shared with other clients or companies.
1 server · DEV/UAT and production share this server, with their applications and databases hosted together.
Back to plan details ↑

Dedicated Production

One DEV and UAT server and one production server. Each contains its own application and database.
2 servers · Each environment has its own server, each containing the application and database.
Back to plan details ↑

High Availability

A node balancer distributes live traffic to two simultaneously active production servers running the same application. Both servers are in service, not a standby pair. Both active application servers use the active production database. The second database is a passive standby that receives replication and activates if the active database fails. Application traffic then switches to the newly active database. A separate DEV and UAT server contains its own application and local database. The external monitoring service monitors both active App Servers.
5 servers + node balancer + external monitoring. Both production servers run the same application simultaneously and serve live traffic. The databases are active/passive: the standby receives replication and activates if the active database fails. Both application servers then use the newly active database. DEV/UAT includes its own local database.
Back to plan details ↑
Recovery language

Three terms worth understanding.

These service objectives help match the infrastructure plan to the actual business impact of an outage.

RPO

Recovery Point Objective

The target maximum amount of recent data that could be lost after an incident. A lower RPO means more frequent or more continuous data protection.

RTO

Recovery Time Objective

The target time to restore production service after a qualifying infrastructure outage. More resilient tiers reduce the amount of manual recovery required.

SLA

Response Time

The target time for 417 Solutions to acknowledge a qualifying critical infrastructure incident and begin active investigation. Response time is not guaranteed resolution time.

Managed infrastructure

You are buying an operated production service — not raw hosting.

Included management time covers the recurring operational work required to keep the production environment healthy, protected, monitored, and recoverable.

Monitoring and alert review
Backup and recovery checks
Security and platform maintenance
Infrastructure troubleshooting
Certificate and environment administration
Production infrastructure changes within allowance

Shared Production: The production (PROD) environment shares one server with your own development and user acceptance testing (DEV/UAT) environments. That server is dedicated to your organization; nothing on it is shared with other tenants, clients, or companies.

Service notes: RPO, RTO, and response times are operational targets rather than absolute guarantees. Actual recovery can vary based on the nature of the incident, data volume, third-party availability, and whether the issue is infrastructure- or application-related.

A Severity 1 / critical infrastructure outage means the production application is unavailable to substantially all users or a major infrastructure failure materially prevents normal production use.

Included infrastructure-management time applies to routine hosting administration, monitoring, recovery checks, security maintenance, infrastructure troubleshooting, and related platform work. New application features, application redesign, substantial code changes, data corrections, and unrelated project work are outside the included allowance and may be billed separately.

*High Availability has a 10-minute database RPO target for managed MySQL point-in-time recovery when the required backups and transaction logs are available. This describes the age of recoverable data, not the time to restore service. Recovery from external backups has a separate 1-hour RPO target. Automatic failover may restore service sooner than the published RTO; backup restores, regional outages, accidental deletion, or application-level corruption may require a longer recovery process. Targets are confirmed for the application and are not guarantees.