Laravel and PHP runtime
Host a real Laravel application with web requests, scheduled tasks and background workers considered as part of the environment.
Managed application hosting
Run your Laravel application on infrastructure built for it.
Host Laravel, PostgreSQL, Redis, Docker and Git-based deployment on Technolutions Cape Town VPS infrastructure, sized around what the application actually needs.
Laravel / PHPPostgreSQLRedisDocker ComposeGitHub deploys
GitHub repositoryCode and deployment workflow
Laravel application layerWeb, workers and scheduled jobs
PostgreSQL and RedisDatabase, queues, sessions and cache
S3-compatible storageDocuments and uploaded files
The stack
Everything a production Laravel application needs, arranged around the workload.
This is for applications that need more than brochure hosting. The application, database, cache, queues, files and deployment workflow are treated as one production environment.
PostgreSQL database
Run the application database on infrastructure sized around the workload instead of forcing it into a generic shared-hosting pattern.
Redis queues and cache
Give sessions, queues and cache a dedicated layer so background jobs do not fight the web application for the same resources.
Docker and Compose
Define the application, workers, database and cache in a repeatable container-based environment.
GitHub-based deployment
Deploy from a repository and defined workflow instead of editing files directly on the production server.
S3-compatible document storage
Keep uploaded files and generated documents away from the application server disk where that makes sense.
How it fits together
Your application, data and jobs sit on the right layers.
Web traffic, database work, background queues and document storage should not all compete for the same space. Splitting the layers makes the environment easier to operate and recover.
CodeGitHub repository
RuntimeLaravel application
ContainersDocker Compose
DataPostgreSQL
Queues and cacheRedis
FilesS3-compatible storage
Backups
Application recovery needs more than a full-server image.
Server-level backups protect the machine. Application-level and database-level backups give you a narrower recovery option when the issue is a bad deployment, a failed migration or an accidental delete.
Server-level backup protects the operating system, server configuration and full disk state.
Database backups support narrower recovery from bad migrations, deleted records or application-level mistakes.
Application files and deployment history can be protected separately from the full server image.
Best suited for
Applications that already matter to the business.
Custom internal systems that staff use every day.
We scope the hosting around the current application, expected users, data volume and recovery expectations.
Document-heavy workflows such as document management systems.
We scope the hosting around the current application, expected users, data volume and recovery expectations.
Laravel applications with queue workers, scheduled jobs and file uploads.
We scope the hosting around the current application, expected users, data volume and recovery expectations.
Business portals where shared hosting is too limiting but a bare VPS is too hands-on.
We scope the hosting around the current application, expected users, data volume and recovery expectations.
Questions answered
What to know before moving your application here.
Is this just a normal VPS?
No. A VPS gives you infrastructure. Application hosting scopes the runtime, database, cache, deployment workflow, storage and backup approach around the application itself.
Does this replace the normal VPS backup?
No. Server-level backup still protects the whole machine. Application and database backups add a narrower recovery option for bad deployments, accidental deletes or database-level issues.
Can this support a non-Laravel PHP application?
Possibly. The page is written around Laravel because that is the target stack, but similar PHP applications can be scoped after reviewing the runtime, dependencies and deployment method.
Do we need to already use GitHub?
No. GitHub is the preferred deployment route, but if your team is using GitLab, Bitbucket or another workflow, we can confirm whether the same deployment approach applies.
Application hosting
Tell us what your Laravel application needs to run well.
Share the application stack, users, database size and current hosting setup, and we will scope the right environment.