Frequently asked questions
Answers about servers, GitHub, databases, domains, deployment, and payments.
Do I need to bring my own server?
No. Openstead supplies and manages the infrastructure used by your services. You connect source code or a container image and configure the application.
Can I deploy a private GitHub repository?
Yes. Connect the Openstead GitHub App and grant it access to the repository. GitHub account sign-in alone does not grant repository deployment access. Organisation installations may require an organisation owner. See GitHub.
Does Openstead detect my framework?
Openstead inspects supported application files when a repository is selected. It can propose runtime, directory, and build settings. Review the result for monorepos and unusual project layouts. A Dockerfile is available when you need explicit control of the build environment.
Can I run Laravel with MySQL?
Yes. Deploy Laravel as a web service, create MySQL in the same environment, and add database connection references. Put uploads on persistent storage and preserve the application's existing encryption key when migrating. See Laravel.
Can I connect to a database from my laptop?
Managed database ports are private to Openstead applications in the same environment. There is no public PostgreSQL, MySQL, or Key Value address to paste into a desktop database client. MySQL includes phpMyAdmin, opened securely from the dashboard.
Will application files survive a deployment?
Only files stored on the service's configured persistent disk are intended to survive container replacement. Treat other writable container files as temporary. A managed database includes its own persistent data storage. Database backups do not include uploaded application files.
Can I use my own domain?
Yes, on web services and static sites. Add the hostname, publish the supplied ownership TXT and routing record, and allow Openstead to verify DNS and activate HTTPS. Cloudflare records must use DNS-only mode for the current verification flow. See Custom domains.
Why does a free application take time to open?
A Free web instance sleeps after inactivity and starts when a visitor arrives. Paid web instances do not use the free idle-sleep policy. Static sites and MySQL Free also do not use that policy.
Do I have to save a card?
No. Paid service months use hosted checkout. Renewal is manual, with an invoice issued two days before the current month ends. A three-day grace period follows expiry; unrenewed compute then pauses and database data and persistent disks are retained. See Renewals.
Does a successful payment mean my application is live?
No. Confirmed payment purchases capacity, then provisioning and deployment run separately. If a paid deployment fails, review its deployment error and use the available retry flow. Check the existing purchase before paying again.
How do I get help?
Check System status for known platform incidents and maintenance. Review incident updates and history without signing in to the Openstead console. Read Platform status and incidents for the difference between platform availability and an individual application's health.
Contact Openstead support. Include the service name or ID, the time of the problem with a timezone, the deployment or request ID, and the relevant error text. Describe what you expected and what happened. Remove passwords, API keys, database URLs, payment details, and customer data from logs or screenshots.