A project is one app or scheduled job on JustDeploy. Open it to see its link or schedule, updates, settings, and activity.
A Scheduler project runs your code on a repeating schedule instead of serving web traffic. Great for nightly reports, cleanups, syncs, and other recurring tasks.
Pick how often it runs (every few minutes or hours, daily, on specific weekdays, or monthly) and the time, right in the console. You can add several schedules (say, a morning run and an evening run) and describe each in plain words like "every weekday at 9am". New schedulers start with one schedule; open the project to add, edit, or pause them anytime.
Pause a schedule to stop runs without deleting anything, then resume when you are ready. Run now triggers a run immediately, which is handy for testing. Output from every run shows up in Logs.
Once deployed, your app gets a URL where you (or your users) can visit it. Find it on your project page.
$0.004 for each minute your app spends working. It comes out of the same credit as your files and your email, so there is no separate hosting bill, and the $4 of free monthly credit covers around 16 hours of work if you spend it all here.
Working means the minutes your app actually spends handling a request or running a scheduled task, not the time it sits deployed. An app that handles no requests today uses no compute credit today. A Scheduler that runs for ten seconds a night is charged for those ten seconds. Stored files and email are charged separately.
See how your app is doing with built-in metrics: Requests (how many times it was called), Response Time (how fast it responds), and Requests at once (how many requests it handles at the same time). View data across different time ranges from 1 hour to 30 days.
Environment variables are settings your app needs, like a key for another service it talks to. Usually your coding AI sets these up while wiring things together; you can also view or add them yourself in the project’s Advanced section.
Restrict who can reach your app by allowing specific IP addresses. Most apps don’t need this. Manage rules in the project’s Advanced section; blocked attempts appear in your logs (filter for "[JUSTDEPLOY_FIREWALL]").
Normally every member of your organization can deploy every project. If a project should stay in certain hands, open the project and pick its managing members: from then on only they can deploy it or copy its deploy guide, whatever their role. Even an owner who is not picked is refused. Pick no one to open it up again.
If your AI reports that a project is managed by designated members, this setting is doing its job. Ask one of the managing members to do the deploy, or change who is picked on the project’s page in the console. Any member can make that change; it just cannot be done from outside the console, which is the point.