Server Requirements
Ensure your environment meets these requirements for a smooth installation and operation of Prodly â the AIâpowered product description generator built with Next.js 14, Supabase, and modern AI APIs.
Prodly can be deployed in two ways:
⢠Fully managed on platforms like Vercel or Netlify (recommended for most users)
⢠Selfâhosted on your own VPS or dedicated server
Important: Shared hosting (cPanel, traditional hosting) is not supported. Prodly requires a Node.js runtime and access to a PostgreSQL database.
Core Requirements
Prodly relies on a modern JavaScript runtime and a PostgreSQLâcompatible database.
If you use Supabase (our recommended database), the PostgreSQL version is automatically managed.
Node.js: Version 18.x or later (LTS recommended)
PostgreSQL: Version 14.x or later (if selfâhosting)
Redis: Required for rate limiting â we recommend Upstash (serverless Redis)
API Keys: Groq, Google Gemini, Serper (see Environment Variables)
When using Supabase, you donât need to manage PostgreSQL yourself â simply create a project and copy the connection credentials.
Recommended Hosting Platforms
Vercel (optimal)
Prodly is a standard Next.js application and works flawlessly on Vercel.
Zeroâconfiguration deployment â just connect your GitHub repository.
Netlify
Also fully compatible via the Next.js runtime adapter.
Selfâhosted VPS
If you prefer full control, you can run Prodly on any VPS that meets the specifications below.
Vercel â effortless deployments
Netlify â great for Next.js
Railway â allâinâone platform
SelfâHosting: Minimum VPS Specifications
If you choose to selfâhost, your server should have:
Memory: 2 GB RAM (4 GB recommended)
CPU: 2 vCPUs or more
Recommended VPS providers:
- DigitalOcean â affordable, SSDâbacked droplets
- Hetzner â excellent EUâbased performance
- Vultr â global presence, competitive pricing
- Linode â reliable and developerâfriendly
- AWS EC2Â â for enterprise scalability
For testing and small to medium loads, a 2 vCPU / 4 GB RAM VPS from Hetzner or DigitalOcean works perfectly.
Required Ports (for selfâhosted)
Make sure the following ports are open in your firewall:
| Port | Purpose |
|---|---|
| 3000 | Next.js development server (optional) |
| 443 | HTTPS traffic (production, with reverse proxy) |
| 80 | HTTP â for Letâs Encrypt certificate setup |
| 5432 | PostgreSQL (if selfâhosting the database) |
If you use a managed database (Supabase, Neon, etc.), port 5432 is not needed on your server.
Web Server & Reverse Proxy
While Prodly can run directly via next start, we strongly recommend using Nginx as a reverse proxy in production to handle SSL, caching, and compression.
Nginx: Recommended for proxying requests and SSL termination
Apache: Not recommended unless used only as a reverse proxy
See our Deployment Guide for sample Nginx configuration.
Environment Variables
Prodly requires several environment variables for authentication, AI services, and rate limiting.
All variables are listed in the Environment Setup section.
Never commit your .env.local file to version control. Use your hosting platformâs secret management (e.g., Vercel Environment Variables).
Whatâs Next?
Once your server or hosting platform meets these requirements, proceed to the next step:
Set up your environment variables and install ProdlyNeed help choosing the right infrastructure? Contact our support team.