Your AI prompts are trapped
in your codebase
Your content team edits prompts in a clean, guided UI. Every change flows through GitHub — full version history, optional PR reviews, zero risk to your codebase.
You are a helpful customer support assistant for
Acme Corp. Your tone should be {{tone}}
and you should respond in {{language}}.
Always greet the customer by name when available.
Never share internal pricing or roadmap details.
GitHub-native
Built on the GitHub App platform
Zero prompt content stored
Content passes through, never persisted
< 2 min setup
Install, connect, start editing
Free forever tier
1 repo, 2 editors, no credit card
The problem
Prompt changes shouldn't need a developer
Developers are the bottleneck
Every prompt tweak needs a developer to open a PR, review, and merge. Your content team waits days for a one-word change.
Direct repo access is risky
Giving non-technical users write access to your codebase is a security and stability risk you can't afford to take.
No visibility into changes
Who changed what, and when? Without an audit trail, debugging prompt regressions is slow and painful.
Who it's for
Built for every stakeholder in the loop
Different roles need different things from prompt management. Here's how each one benefits.
For Developers
Install once, stop being the bottleneck for every prompt change.
Connect your repo, mark which files are prompts, and set review rules. Your content team handles the rest — you stay in control without being in the loop for every change.
For Content Teams
Edit prompts safely. No Git, no CLI, no risk.
A clean editor with variable highlighting. Make changes, see diffs, and ship — no technical setup required.
For Engineering Leads
Full audit trail and PR workflow for every change.
Every edit has a complete audit trail — author, timestamp, and diff. Enforce PR reviews, manage access by role, and keep your codebase safe while unblocking your team.
Features
Built for teams that ship AI products
Your prompts stay in GitHub
We read from and write to GitHub on your behalf, but never store, cache, or log prompt content. Your repo is the single source of truth.
Flexible review controls per file
Set each file to push directly or require a PR. PRs land in GitHub where any team member can review and approve — no code knowledge needed.
Works with your existing files
No migration, no new format. Edit .txt, .erb, .js, .py — whatever your codebase uses. PromptDeploy edits the real files, not an abstraction layer.
Scoped access by role
Editors can only touch prompts. Developers configure repos. Admins manage billing and team. No one sees more than they should.
Know which prompts are working
Collect thumbs-up/down feedback from your users via a simple API call. Iterate based on real data, not guesswork.
Fits into your existing toolchain
Read prompts and send signals via a simple REST API. Works alongside your existing stack — nothing new to adopt.
The editor
A prompt editor your whole team can use
No Git knowledge required. Variables are highlighted, changes are tracked, and everything flows through your existing GitHub workflow.
# Welcome flow - shown to new users after signup
Welcome to {{company_name}}, {{user_first_name}}!
I'm your AI assistant. I can help you with:
- Setting up your workspace
- Understanding your {{plan_name}} plan features
- Connecting your first integration
My tone should be {{tone}} and I should keep
responses under {{max_words}} words unless asked to elaborate.
Review & approve
Every prompt change gets the review it deserves
When PR review mode is on, editors propose changes and a pull request opens on GitHub — no code editing required. The team reviews the diff, approves, and merges when ready.
Editors propose
Changes open a PR automatically. Editors don't need Git or a GitHub account.
Review on GitHub
The PR appears in GitHub where the team can see the diff, check what changed, and approve. No code to read.
Changes merge
Merge the PR on GitHub and the prompt goes live with a full audit trail.
Update welcome tone from "friendly" to "warm and professional"
Clear diffs — see exactly what the editor changed, line by line
No code knowledge needed — reviewers see plain-English prompt text, not source code
One-click merge — approve and merge the PR directly on GitHub
Pricing
Simple, transparent pricing
Start free. Upgrade when your team grows.
Free
For getting started
- 1 connected repo
- 2 team seats
- 1,000 signals/month
Team
For growing teams
- 5 connected repos
- 10 team seats
- 10,000 signals/month
- PR workflow
- Variable highlighting
- Audit log
Business
For scaling organisations
- Unlimited repos
- Unlimited seats
- 100,000 signals/month
- PR workflow
- Variable highlighting
- Audit log
- Priority support
- Repo access controls
No long-term contracts. Cancel anytime. Your prompts stay in GitHub.
FAQ
Common questions
Do you store our prompt content?
No. Prompt content passes through our server to broker GitHub API calls, but is never stored, cached, or logged. It's fetched from GitHub, displayed in your browser, and written back to GitHub. Nothing is persisted on our side.
Is there vendor lock-in?
None. PromptDeploy reads and writes directly to your GitHub repo. Remove the app and your files are completely untouched. Every prompt, every edit, every piece of history stays in Git where it belongs.
Can we export our data?
There's nothing to export. Your prompts already live in your repository. Every change is a real Git commit with full authorship and history. You own the data from day one.
What happens if PromptDeploy shuts down?
Your prompts are safe in GitHub, so nothing is lost. You'd lose the editing UI and collaboration features, but every prompt file, every version, and every commit remains in your repo exactly as it was.
Do editors need GitHub accounts?
No. Editors sign up with email and are invited to your organisation. The GitHub App handles all repository operations on their behalf using the developer's installation.
Can editors break our codebase?
Editors can only modify the specific files that developers have marked as editable prompts. They can't access other files, branches, or settings. For extra safety, enable PR review mode so changes open a pull request on GitHub — anyone on the team can review and approve before merging.
Do I need a developer to use PromptDeploy?
Only for the initial setup. A developer installs the GitHub App, connects your repo, and marks which files are editable prompts — typically under 10 minutes. After that, editors can make prompt changes independently. If you enable PR review mode, changes open a pull request on GitHub where anyone on the team can review and merge — no developer involvement required. Developers are only needed again for more complex changes like adding new prompt files, restructuring code, or adjusting repository settings.
What file formats are supported?
Any text file in your repo: .txt, .md, .erb, .js, .py, .yaml, and more. PromptDeploy edits the actual files in your codebase, not an abstraction layer.
Do I need a credit card to start?
No. The Free tier is free forever: 1 repo, 2 editors, no credit card required. You only enter payment details when you choose to upgrade to a paid plan.
What are Prompt Signals?
Signals are thumbs-up/down feedback events sent from your app via our API. They help you track how each prompt is performing with real users, so your team can iterate based on data rather than guesswork.