Starter
A personal website, small business site, or lightweight PHP application.
- 1 website
- 0.25 shared vCPU budget
- 512 MB RAM
- 5 GB persistent storage
- 64 process budget
- Compatible FrankenPHP, NGINX, or Apache
Start with a measured workload and define when you would need more capacity. No startup discount or programme entitlement has been published.
One plan budget shared across your websites. Prices exclude applicable taxes.
A personal website, small business site, or lightweight PHP application.
A growing application or a small portfolio with a shared resource budget.
A larger website portfolio with more memory, storage, and processing capacity.
Define application count, capacity, access, recovery, and operational support before a custom proposal.
Annual prices equal 12 monthly payments; no discount or free domain is implied. Domains, managed databases, bandwidth allowances, and backup retention are scoped separately. Ordering and production activation are not enabled.
Begin with a staging application and a measured resource baseline. Include database capacity, storage, domain renewal, recovery, and the expected traffic profile in the budget. No startup discount programme is currently published.
List the PHP version, required extensions, web engine dependencies, and writable paths. Verify login, routing, uploads, and representative business workflows in staging.
Observe CPU, memory, database latency, disk growth, and background work under a representative workload. Keep cold-start and warm behaviour separate.
Validate the source revision, build output, readiness check, and rollback artifact. Test restoration of persistent data independently.
Request published capacity, limits, availability, backup retention, support responsibilities, and final terms before committing production traffic.
Ask for a stated allowance, limit, and owner for each part of the service.
Identify the application and environment count, selected PHP engine and version, resource policy, persistent services, domain requirements, backup scope, and support responsibilities. State limits and any chargeable overage before an order is accepted.
The initial catalogue publishes base prices and plan budgets. It does not activate a subscription or accept payment. Confirm service availability, additional charges, and final service terms before placing a production order.
Self-service checkout is not currently published. Review the intended service model here and confirm availability before moving a production application.
Domain registration is a separate registrar transaction. Dynadot is the selected provider boundary; registration and renewal require an activated provider integration.
No. The runtime contract covers general PHP applications. Each application still needs a compatible PHP version, extensions, document root, and writable path configuration.
Bring your PHP application, choose the runtime it needs, and keep releases, domains, and operations together in your Orisite panel.