Skip to main content

pdt - process deploy tool

Turn any script into a scheduled job in your cloud.

pdt builds, runs, and deploys scheduled jobs to AWS, Azure, Google Cloud, or Windows Task Scheduler. It gives every job the same primitives, chosen from years of deploying scheduled jobs for businesses on each cloud. No servers to run and nothing extra to install, and everything it makes lives in your own account.

What pdt does: your project folder goes through pdt deploy to a schedule on AWS, GCP, Azure, or Task Scheduler, and pdt runs, logs, health, and gui read the results back.

Key Features

  1. Bring your scripts - Drop in your PowerShell or Python files. pdt finds what they need and runs them.
  2. One command to deploy - No cloud skills needed. pdt deploy installs the tools it needs and opens the sign-in page for you.
  3. Any cloud - Move a job between AWS, Azure, Google Cloud, and Windows by changing one line.
  4. Know the cost first - See the plan and a monthly cost estimate before anything changes.
  5. Know when it breaks - Health checks, logs, a dashboard, and alerts to Slack, Teams, or email.

Primitives

Every job gets the same building blocks. pdt picks the service on each cloud for you.

AWS Azure Google Cloud Windows
Compute AWS Batch (Fargate) Container Apps Jobs Cloud Run Jobs Task Scheduler
Schedule EventBridge Scheduler Container Apps Jobs Cloud Scheduler Task Scheduler
Secrets Secrets Manager Key Vault Secret Manager .env file, read at each run
Storage (job files and state) S3 Blob Storage Cloud Storage %ProgramData%\pdt
Logs CloudWatch Logs Log Analytics Cloud Logging Log files
Alerts Slack, Teams, email Slack, Teams, email Slack, Teams, email Slack, Teams, email

Practices

  1. One folder per job - Each job is built, deployed, and destroyed on its own.
  2. Run it locally first - pdt run runs the job the same way the cloud does, with the same config and storage.
  3. You own everything - Your jobs live in your own git repo, and they run in your own cloud account. There is no pdt server.
  4. Secrets stay secret - Kept in .env on your computer and in the cloud's secret store, never in git or the image.
  5. Nothing left behind - Everything pdt makes is tagged managed-by=pdt, and pdt destroy removes all of it.
  6. Cheapest by default - Jobs run only when scheduled, on the lowest-cost option that works (for example arm64 on AWS).
  7. One run at a time - A job's saved state is locked during a run, so two runs never overwrite each other.

Quick Start

Windows

Download and run the pdt installer.

macOS / Linux - with uv

Install uv, then pdt:

curl -LsSf https://astral.sh/uv/install.sh | sh
source $HOME/.local/bin/env
uv tool install pdt-cli
uv tool update-shell

For other ways to install, and how to update or remove pdt, see docs/install.md.

Deploy your first job

Then run:

pdt init jobs
cd jobs
pdt new hello-powershell --from powershell-hello-world
cd hello-powershell
pdt run
pdt deploy
pdt logs

Deploy your own script

  1. Create the job with pdt new your-powershell-job --from powershell-hello-world
  2. Replace hello.ps1 in the your-powershell-job folder with your own .ps1 script
  3. Test the job locally with pdt run your-powershell-job
  4. Deploy it with pdt deploy your-powershell-job

See every command.

Example deployment

A first deploy of the hello-world-example app to Azure, then a look at its run:

pdt deploy hello-world-example: the plan, the monthly cost estimate, the build, and the first run's log, followed by pdt logs, pdt health, and pdt run --deployed.

See the same output as text.

The bundled examples

Run pdt examples to list them, then pdt new <name> --from <example> to copy one.

hello-world

Small job that logs "Hello world." pdt init puts a copy of this in every new empty project.

azure-license-waste

PowerShell job. Finds the Microsoft 365 licenses a tenant pays for that nobody uses: paid licenses on disabled accounts, on accounts that have not signed in for 90 days (or never did), and seats bought but assigned to nobody. Each run keeps a LicenseWaste-<date>.xlsx workbook in the job's data store, with a Summary sheet of monthly and annual cost and one sheet per finding.

impossible-travel-report

Looks at recent Entra ID sign-ins. Sends an email when one person signs in from two far-apart places too quickly: Dallas an hour ago, Paris now.

Settings for the lookback window, the minimum distance, and the email addresses live in the job's own pdt.yml. The env vars it needs are listed there too, and in its env.template.

intune-export

PowerShell job. Once a week it exports the Intune configuration of a tenant with the bulk export of IntuneManagement version 4, and keeps an IntuneExport-<date>.zip in the job's data store. To import, unzip it and point IntuneManagement's import at the company folder inside.

monday-orphaned-account-report

Reports active Monday users whose email address does not match the userPrincipalName of an active Entra ID user.

powershell-hello-world

A PowerShell job whose one script, hello.ps1, writes "Hello, world!". It is the job the Quick Start deploys. Put your own .ps1 files in its folder in place of hello.ps1 to deploy your own PowerShell job.

powershell-report

PowerShell job. small CSV report with Export-Csv, and pdt keeps the file in the app's data store.

web-hello

A web app (app_profile: web) that greets the person who signed in.

Support

AutoIDM makes pdt. Any issues, questions, ideas, or concerns? Use any of these methods to get a hold of us:

  1. Discord
  2. Report a problem at https://github.com/AutoIDM/pdt/issues.

Documentation

  • Projects and apps: set up a project, add an app, and where pdt keeps its files
  • Deploying: deploy, run, pause, and destroy a job, and run pdt from CI
  • Commands: every pdt command and its options
  • Settings: every setting in the project's and the apps' pdt.yml files, and every env var, with its allowed values and its default
  • Choosing where jobs run: AWS, Azure, Google Cloud, Windows Task Scheduler, and your own Dockerfile
  • Keeping files between runs: the storage folder every app gets, and state that carries from one run to the next
  • The dashboard: pdt gui, the browser view of every app's runs, logs, and files
  • Writing your own app: Python and PowerShell apps, and logging
  • Sending email: send mail from an app over SMTP, Microsoft Graph, SES, or Resend
  • More ways to install: other installs, and how to update or remove pdt
  • Concepts: projects, apps, and app profiles
  • Types of apps: scheduled jobs and web apps, and the services pdt picks for each one on each cloud

Metadata

Release files for pdt-cli 0.1.15

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for pdt-cli 0.1.15
File Size Uploaded Provenance Actions
pdt_cli-0.1.15.tar.gz 590.3 kB With provenance Details for pdt_cli-0.1.15.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for pdt-cli 0.1.15
File Interpreter ABI Platform Actions
pdt_cli-0.1.15-py3-none-any.whl Python 3 none any Details for pdt_cli-0.1.15-py3-none-any.whl

Total release size: 972.0 kB

Release files / pdt_cli-0.1.15.tar.gz

Download URL pdt_cli-0.1.15.tar.gz
Size 590.3 kB
Tags Source
SHA-256 checksum
How to use checksums
a8893817493ad21df2c8f80fc84b1728bf57e74a4fe6852832a90aa69ba42a87
BLAKE2b-256 checksum
How to use checksums
1b6875ebba23fbdafb1efc8b570aa893ef6384bdce54abef375754a89792d1cf
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 13, 2026.

Transparency log

Release files / pdt_cli-0.1.15-py3-none-any.whl

Download URL pdt_cli-0.1.15-py3-none-any.whl
Size 381.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
7310100b6d14ebc3471a3300f304db736639d6228f27160fb2a4d66ecd7e6e54
BLAKE2b-256 checksum
How to use checksums
be4c87434c3920662d00ccc76d90b2db3c2314652d54cd7aa7cc5040aa5d7d64
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 13, 2026.

Transparency log

Security for pdt-cli 0.1.15

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for pdt_cli-0.1.15.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 13, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page