Deploy a GitHub App in Saudi Arabia with Raseef
A practical guide for SaaS founders: deploy a GitHub app in Saudi Arabia, connect PostgreSQL privately, configure HTTPS and prepare for your first users.
Your SaaS prototype works locally. The next milestone is not another infrastructure diagram: it is a reliable URL that a potential customer can open.
For a developer or small founding team building for Saudi Arabia, that first release usually needs three things: a web service, a database and a repeatable way to ship changes. This guide shows how to put those pieces together on Raseef, from a GitHub repository to an HTTPS application hosted in the Kingdom.
Raseef is currently onboarding teams through a private pilot. Request access if you do not yet have an account, or use the steps below to prepare your repository.
What your first deployment should look like
Start with the smallest architecture that supports a real customer journey:
| Component | Purpose | Exposure |
|---|---|---|
| Web app or API | Serves your product | Public HTTPS |
| PostgreSQL | Stores application data | Private, in the same environment |
| Database volume | Keeps database files across deploys | Attached to the database |
Keep the web app stateless where practical. Do not assume files written inside its container will survive a deployment; use a volume when you need persistent files.
Raseef's documentation states that services and the data they keep are hosted in Saudi Arabia. Separately review where any external services you connect—such as analytics, email or payment providers—process the data you send them.
1. Prepare the GitHub repository
Before opening the console, check these basics:
- You own the personal GitHub account, or you are an owner of the GitHub organization you will connect.
- The repository has a working production start command.
- The application reads its listening port from
PORTand binds to0.0.0.0, not justlocalhost. - Required configuration is documented in a file such as
.env.example, without real credentials.
For an existing Express app, the listening configuration can look like this:
const port = Number(process.env.PORT || 8080);
app.listen(port, '0.0.0.0');Raseef can build from a repository with or without a Dockerfile. For a monorepo, check that you select the correct app and root directory. See the GitHub deployment guide for connection permissions and source settings.
2. Connect GitHub and deploy the service
In the console, choose New project → GitHub Repository, connect GitHub, then select the repository and branch. The Raseef GitHub App requests read access to the repositories you select.
Choose Deploy Now to build and deploy. If Raseef detects declared variables, it shows Add Variables instead: configure those values before deploying. Follow the build in Builds and application output in Logs.
For the customer-facing service, use Public web (HTTPS), or configure Public HTTP under Networking, with the port your app actually listens on. A successful public deployment gets an HTTPS address on raseef.run.
Open that address and test an actual product route, not only the landing page. The quickstart walks through this console flow.
3. Connect PostgreSQL without exposing it publicly
In the same project and environment, choose Create → PostgreSQL and name the service db. The template creates its own volume and a generated password.
In the web app's Variables, add:
DATABASE_URL=${{ db.DATABASE_URL }}This reference resolves to the database connection string when the application deploys. It avoids copying a password into your source code and uses the database's private address.
Deploy the database before deploying the application that references it. Saving variables alone does not change the running application: deploy again to apply them. If a referenced database value changes later, redeploy the consuming application when ready.
The private network is scoped to services in the same environment; another project or environment cannot reach that private address. See variable references for the exact behavior.
4. Make the next release as deliberate as the first
Before inviting users, configure an HTTP readiness check such as /healthz that responds successfully only when the app is ready to serve requests. A listening TCP port alone does not prove that your application has finished starting.
For services without a volume, Raseef rolls out the new version alongside the current one and moves traffic after readiness succeeds. A service with an attached volume restarts during deployment and can have a short interruption. Plan accordingly.
Rollback restores a previous service image and settings within your plan's rollback window. It does not undo database migrations or restore database contents. Prefer backward-compatible schema changes so that the previous application version can still run if you need to roll back. Review the deployment guide before your first update.
Automatic deployment on every push is optional and off for a new service. Enable it when your branch and release workflow are ready; recheck it after changing source settings, which turns it off again.
A launch checklist for your first SaaS users
- Open the HTTPS URL and complete one end-to-end journey, such as signup and creating a record.
- Restart or redeploy the app, then confirm the record is still in PostgreSQL.
- Check startup and request logs without printing credentials.
- Confirm the readiness endpoint reflects real application readiness.
- Review volume and backup behavior: paid plans include volume backups; the free plan does not. Define and test your recovery process.
- Add a custom domain when you are ready to share your product's own URL.
- Review platform limits and pricing against your expected workload.
Build the product, then improve it with real feedback
The useful outcome is not simply a green deployment status. It is a customer who can open your app, complete a task and come back to saved data—and a team that knows how to ship the next improvement.
Raseef brings GitHub deployment, private service connectivity and public HTTPS into one workflow, with your workloads hosted in Saudi Arabia. Start with one app and one database, validate the customer journey, and expand when the product needs it.
Request access to the Raseef private pilot to take your repository toward its first live release. Already have access? Follow the quickstart in the console.