Recommended Free Tools
Run Supabase on your own VPS by deploying Supabase’s official Docker Compose stack as a Docker Compose service in Coolify. Coolify handles deployment, reverse-proxy routing, domains, and environment-variable management; Supabase still runs as a group of containers that you must size, secure, back up, update, and monitor.
Antihost offers Linux VPS plans with full root access, unlimited traffic on a 1 Gbps port and a 14-day free trial.
A usable production installation depends on three things: correct public URL variables, persistent Postgres and Storage volumes, and an operational plan for HTTPS, secrets, backups, and recovery.
As an Amazon Associate I earn from qualifying purchases.
What Coolify changes—and what it does not
Supabase is not a single container. Its self-hosted edition is a Docker Compose application containing the database, API gateway, Auth, Studio, Realtime, Storage, image processing, and other services. Supabase’s documentation describes Docker as the fastest and recommended way to self-host, and as the easiest way to get started.
Coolify provides the control plane around that Compose application. You create a server, define a Compose service, supply variables, attach a domain, and let Coolify create the containers and proxy routes. Coolify does not turn Supabase into a managed service: you remain responsible for operating the host, protecting credentials, applying updates, planning capacity, and recovering from failures.
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
The practical model is therefore:
- Supabase Compose: the application definition and its individual services.
- Docker on your server: the runtime for those containers.
- Coolify: deployment orchestration, generated variables, persistent-resource configuration, and reverse-proxy integration.
- You: the owner of data durability, security, maintenance, and incident response.
Choose a server that can run the complete stack
Use a Linux VPS or dedicated server with Docker available. Supabase’s 2026 Docker guidance lists the following baseline. The minimum is intended for running all components, not for a busy production workload.
| Workload target | Memory | CPU | Disk | Qualification |
|---|---|---|---|---|
| All components, minimum | 4 GB RAM | 2 CPU cores | 40 GB SSD | Supabase 2026 minimum for the full component set |
| Larger workload, recommended | 8 GB or more | 4 CPU cores | 80 GB or more SSD | Supabase 2026 recommendation; actual needs rise with traffic and data |
Disk sizing must include more than the operating system. PostgreSQL data, uploaded Storage files, container images, logs, temporary files, and local backup staging all consume space. A server that technically meets the 40 GB minimum can still fill quickly if users upload media or if logs and database files are left unmanaged.
If you do not need every feature, the Compose definition can be reduced. Supabase identifies Realtime, Storage, imgproxy, and Edge Runtime as components that can be removed to lower resource requirements. Remove a component only after checking that your application does not depend on it; deleting Storage, for example, changes how file uploads work.
Skills and access required
- Basic Linux server administration and networking.
- Git, Docker, and Docker Compose familiarity.
- Permission to create DNS records for the hostname you will use.
- Access to a Coolify installation that can reach the target server.
- A plan for SMTP and OAuth credentials if your application will send email or use external identity providers.
Decide your public hostname and recovery plan first
Pick the hostname clients will use before deploying. The same public address must work consistently for browser clients, API clients, and Auth callbacks. Changing it after users sign up can invalidate redirect settings and create confusing mixed-origin failures.
Prepare these values before opening Coolify:
- A DNS record pointing your chosen hostname to the server’s public IP.
- A strong Postgres password and a separate, strong Studio dashboard password.
- Supabase API keys and JWT secrets generated for this instance, stored in Coolify’s secret-capable environment-variable controls.
- SMTP credentials and sender details if password-reset or confirmation email is required.
- OAuth client settings, callback URLs, and secrets for each identity provider you intend to enable.
- An off-host destination for database dumps and a separate copy of Storage files.
Do not treat a VPS snapshot as your only recovery mechanism. A snapshot can be unavailable with the server, provider account, or region that suffered the incident. Recovery should work on a fresh host using independent copies and documented restore steps.
Deploy the Supabase Compose project in Coolify
Use Supabase’s current official Docker Compose definition, or Coolify’s maintained Supabase template when it matches the version and components you need. A template is convenient, but review it just as carefully as a file you pasted yourself.
Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
- Create or select the server. In Coolify, choose a server with Docker installed and enough CPU, memory, and SSD capacity for your selected components. Confirm that the server can accept web traffic through the ports your reverse-proxy design requires.
- Create a Docker Compose service. Start a new Compose resource in the appropriate project and environment. Paste or import the current Supabase Compose definition, or select the maintained Supabase template.
- Inspect the parsed definition. Coolify displays component cards after parsing. Check service names, internal networks, exposed ports, health checks, and every declared volume. A parse that succeeds can still contain an incorrect path or an unintended public port.
- Configure persistent storage. Map a durable volume or bind mount for PostgreSQL data and another durable location for Supabase Storage files. Keep these mappings on storage that survives container replacement.
- Set required variables. Define the public URL variables, database password, dashboard credentials, API keys, JWT secrets, and any SMTP or OAuth settings required by your application. Coolify can enforce required interpolation such as
${NAME:?}, which prevents deployment when a value is missing. - Attach the domain. Configure the hostname in Coolify and route it through the reverse proxy. In production, terminate TLS at the proxy and expose HTTPS on port 443 rather than publishing the API gateway directly to the internet.
- Validate and save. Use Coolify’s validation view to catch malformed Compose syntax and unresolved required variables. Review the deployable definition that Coolify generated before saving.
- Deploy and inspect output. Start the deployment, then read the deployment output and container logs. Wait for database migrations and health checks to complete before testing Studio, the API, Auth, and Storage.
When you change an environment variable or secret, recreate the affected containers. Editing a value in Coolify does not retroactively change a process that is already running with the old environment.
Configure the URL variables correctly
URL configuration is the most common source of a deployment that appears healthy but fails for real users. Use the externally reachable HTTPS hostname, not an internal container name or the server’s private address.
| Variable | What it controls | How to choose the value |
|---|---|---|
SUPABASE_PUBLIC_URL |
Base URL used by Dashboard, API, and Storage | The public HTTPS origin clients will open |
API_EXTERNAL_URL |
External API address used when configuring Auth callback behavior | The API URL reachable from the internet through your proxy |
SITE_URL |
Default Auth redirect destination | Your application’s canonical site URL, not the internal Supabase service address |
If your frontend and API use different hostnames, document that arrangement explicitly and configure every Auth redirect and OAuth callback to match. A redirect URI that differs by scheme, hostname, port, or trailing path can be rejected even when the service itself is running.
Set passwords, JWT secrets, and optional integrations
Studio uses HTTP Basic Authentication and requires a secure dashboard password before it starts. Do not leave example credentials in the Compose file or commit secrets to a Git repository. Use Coolify’s environment-variable controls, restrict who can view them, and rotate them if a team member or provider account changes.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minutePostgres credentials, API keys, and JWT-signing secrets are different classes of secret. A database password controls direct database access; API keys control client capabilities; JWT secrets determine token validation. Keep each value unique to this installation and record a controlled rotation procedure before launch.
SMTP and OAuth are optional at first but become operational dependencies when enabled. Verify sender-domain authentication, provider rate limits, callback URLs, and failure notifications. Test a confirmation email, a password reset, and an OAuth sign-in using a non-administrator account.
Rank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
Make Postgres and Storage durable
Container filesystems are disposable. If PostgreSQL data exists only inside a container layer, recreating that container can destroy the database. The same principle applies to uploaded files.
Supabase’s default self-hosted Storage writes files to the server filesystem through a bind mount. In Coolify, ensure that the Storage path resolves to a persistent host directory or volume and that the Docker process can read and write it. Apply the same care to the PostgreSQL data directory.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Check durability by recording the exact host paths or volume names, then recreate a non-production container and verify that data remains. Do not test destructive recreation against your live database without a verified backup and a maintenance window.
Put HTTPS and network controls in front of the gateway
The default Supabase API gateway listens on port 8000. A reverse proxy can terminate TLS on port 443 and forward requests to that gateway. In a production deployment, expose only the proxy’s public entry point and keep database and internal service ports private to the Docker network or firewall.
- Allow inbound HTTPS and only the administration access needed to manage the host.
- Restrict Postgres so it is not reachable from the public internet unless a documented, controlled use case requires it.
- Use Coolify’s domain and certificate configuration for renewal, then confirm that renewal failures generate an alert.
- Redirect HTTP to HTTPS and verify that cookies, Auth redirects, and API requests use the secure origin.
- Keep Studio behind authentication and avoid exposing it on an unprotected alternate port.
Security is not complete when the certificate is valid. Review firewall rules, operating-system updates, Docker access, Coolify team permissions, and the list of people who can read production secrets.
Validate the installation before inviting users
Perform a short acceptance test after deployment and after any major update:
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteRank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
- Open the public hostname over HTTPS and confirm the certificate and redirect behavior.
- Sign in to Studio using the configured dashboard credentials.
- Create a test table and row, then read and update it through the API using the intended client key.
- Register a test user, exercise email confirmation or the configured OAuth flow, and verify the final redirect lands on your site.
- Upload a small file, retrieve it, and confirm that the file remains available after recreating the Storage container.
- Review container logs for restart loops, failed migrations, authentication errors, and rejected origins.
- Check available disk space and memory after the complete stack is running, not merely after the first container starts.
Keep this test as a repeatable smoke checklist. It gives you a fast way to distinguish an application regression from a proxy, DNS, or secret problem.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Backups: the responsibility Coolify does not remove
Supabase’s update.sh helper backs up configuration files into a backups/ directory, but Supabase states that it does not back up Postgres or Storage data. Configuration copies therefore cannot restore your users, rows, or uploaded files.
Use two independent backup streams:
- Database: schedule engine-specific database dump jobs from Coolify’s database Backups page, then copy the resulting dumps off the server.
- Storage: copy the Storage filesystem data to separate disk or object storage on a schedule that matches your recovery-point objective.
Encrypt backups, limit access, retain multiple restore points, and monitor job failures. At least once, restore a dump and a representative Storage sample onto an isolated instance. Document the order: provision a host, deploy the matching Compose version, restore Postgres, restore files, set secrets and URLs, then run the smoke tests.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Updates without losing the instance
Supabase updates can change images, migrations, environment variables, and service behavior. Read the release guidance for the Compose version you are adopting and schedule maintenance when users can tolerate interruption.
- Confirm recent off-host database and Storage backups and verify that the backup jobs succeeded.
- Record the current Compose definition, image versions, variables, volume mappings, and proxy settings.
- Review release notes for required variable changes or migration steps.
- Update the Compose definition in Coolify, validate it, and deploy during the maintenance window.
- Watch deployment output and logs for migration failures or containers that repeatedly restart.
- Run the acceptance tests before reopening the service.
If a variable or secret changes, recreate the affected containers so the new value is loaded. Keep the previous Compose definition available for rollback, but do not roll back blindly after a database migration; restore from a tested backup when the schema cannot safely move backward.
Troubleshoot by symptom
Coolify reports a missing variable
Find the variable marked as required by Compose interpolation, including expressions such as ${NAME:?}. Define it in the service’s environment controls, save, and redeploy. Check for spelling and capitalization differences.
Studio or the API redirects to the wrong host
Compare the browser’s address with SUPABASE_PUBLIC_URL, API_EXTERNAL_URL, and SITE_URL. Correct the public values, recreate affected containers, and retest Auth callbacks from a clean browser session.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Uploads disappear after a redeploy
Inspect the Storage volume or bind mount in Coolify and verify that it points to persistent host storage. If files were written only to a container layer, recover them from the latest Storage backup before changing the mapping.
Containers restart or the server becomes unresponsive
Check memory pressure, CPU saturation, disk usage, and individual service logs. Compare the host against the 4 GB/2-core/40 GB minimum and the 8 GB+/4-core/80 GB+ recommendation. Remove unused components or resize the server rather than repeatedly restarting containers.
OAuth or email confirmation fails
Verify that the provider’s callback exactly matches the public URL and that SMTP credentials, sender settings, and provider-side restrictions are valid. Read Auth logs while performing a new test sign-in or confirmation.
Operating the stack over time
Monitor more than container uptime. Track disk consumption for Postgres and Storage, memory pressure, restart counts, backup success, certificate renewal, and failed authentication or SMTP events. Set thresholds before the server reaches exhaustion; a full disk can prevent both database writes and useful diagnostic logging.
Keep an inventory of the Compose version, enabled components, public hostnames, secret owners, backup destinations, and recovery contacts. When staff or providers change, rotate credentials and remove unused access promptly.
Scaling is bounded by the single-server design unless you deliberately redesign it. A larger VPS provides more CPU, memory, and disk, but it does not automatically create high availability. Plan maintenance windows, understand which services can be restarted independently, and test recovery before promising uptime targets.
Self-hosted Supabase versus managed Supabase
| Decision area | Self-hosted with Coolify | Managed Supabase |
|---|---|---|
| Operational ownership | You handle updates, secrets, firewalls, monitoring, and recovery. | The provider operates the service layer and supplies managed operational tooling. |
| Data control and isolation | Runs in infrastructure you choose, useful for control, compliance isolation, or an isolated environment. | Uses the provider’s shared or dedicated service arrangements and policies. |
| Recurring infrastructure cost | You pay for the VPS, storage, bandwidth, backups, and administration time. | You pay the managed-service plan and any usage-based charges. |
| Backups | You must create, copy, secure, monitor, and restore database and Storage backups. | Backup features and responsibilities follow the managed plan. |
| Scaling | Resize or redesign your host and operate the resulting changes. | Scaling options are provided within the managed platform’s limits and pricing. |
| Feature scope | A self-hosted instance is a single project; Studio does not support multiple organizations or projects. | Managed account structures and project administration are provided by the service. |
Choose Coolify-hosted Supabase when data control, compliance isolation, or a dedicated environment outweighs the work of running the platform. Choose managed hosting when minimizing infrastructure operations and recovery responsibility matters more than controlling the underlying server.
Quick Recap
Production readiness checklist
- Server meets the selected component set’s CPU, memory, and SSD requirements.
- DNS points the intended hostname to the server before certificate issuance.
SUPABASE_PUBLIC_URL,API_EXTERNAL_URL, andSITE_URLmatch the real client and callback addresses.- Postgres and Storage use persistent volumes or bind mounts.
- Studio has a unique, strong password and is not publicly exposed without authentication.
- API keys, JWT secrets, database credentials, SMTP values, and OAuth secrets are stored in Coolify’s protected variable controls.
- HTTPS terminates at the reverse proxy, with only necessary public ports reachable.
- Database dumps and Storage copies run off-host, are encrypted, and have been restored in a test.
- The update and rollback procedure is written down, including container recreation after variable changes.
- Monitoring covers disk, memory, restarts, backups, certificates, and authentication failures.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Free tools Windows power users keep installed
One-click scans. No signup required.
