Ptero: A GPL v2 Multi-Model AI Chat Wrapper With a WordPress Shortcode
AI Chat with powerful models for free
At a glance
- What is it?
- Ptero is a PHP and JavaScript chat front end that puts several hosted language models behind one interface, stores conversations in the browser, and ships as a WordPress plugin. The repository metadata says Apache-2.0 while the README says GPL v2, and that conflict is the first thing to settle before you deploy it.
- Who is it for?
- Adopt Ptero if you want a ready-made chat interface you can drop into a WordPress page with the [mlp_ai_chat] shortcode, or a small PHP and JavaScript front end you can read end to end before trusting it with prompts. Do not adopt it if you need per-user history, server-side audit trails, or any control over which upstream model actually answers.
- Can I use it commercially?
- Yes. Apache-2.0 is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 3 days ago.
- What is it written in?
- Mainly PHP, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- aminkheddache-dotcom/Ptero1,531 ★ · +425
| Repository | 2026-09-11 | 2026-11-15 |
|---|---|---|
| aminkheddache-dotcom/Ptero | 1.1k | 1.5k |
425 Stars in the last 65 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The Problem Ptero Solves Is Interface Sprawl, Not Model Access
Anyone who compares hosted language models ends up juggling browser tabs. Each provider has its own login, its own quota display, and its own idea of what a conversation looks like. Ptero's answer is a single chat surface with a model dropdown, so switching from one model to another is one click rather than one new account. The README frames the audience explicitly: developers, students, and creators who value privacy and simplicity. The privacy claim is specific rather than decorative. Conversations are stored locally in the browser, and the README states that no chat history is saved on the project's servers. For a student pasting lecture notes or a developer pasting a stack trace, that distinction matters more than the model list. The project is also positioned as non-profit with no paid tier, which explains why the model roster is broad and the feature set is thin. There is no team workspace, no usage analytics, no billing. That is a deliberate shape, and it tells you what the project is optimizing for.
What the Architecture Actually Consists Of
Ptero is a thin client. The README lists the stack as JavaScript, HTML, and CSS on the front end, PHP on the back end for WordPress integration, and a REST API between them. The model providers (DeepSeek, Llama, Qwen, MiniMax, Mistral, and others) are upstream services, not weights shipped in this repository. The described flow sends prompts through the application to an upstream provider and returns responses to the browser. The README claims local history storage, but does not establish every intermediary’s retention policy; inspect the deployed implementation and provider terms before sending sensitive data. Two consequences follow from that shape. First, a self-hosted deployment must understand its provider routing and credential management. Second, browser-stored history can be lost when site data is cleared. There is no export path described in the README, and no server-side record to recover from. If you have ever lost a browser profile, you already know how that ends.
Installing It: Two Paths, One Shortcode
The README describes two installation routes. The end-user route requires no installation at all: visit the hosted instance, pick a display name, which is saved locally on the device, select a model from the dropdown, and start typing. No account and no payment are involved. The self-hosted route is WordPress-specific. You download the plugin from the GitHub repository, upload it to a WordPress site, activate it, and then place the shortcode [mlp_ai_chat] on any page or post to embed the full chat interface. That shortcode is the only concrete integration point the README names, and it is worth noting that it is the entire documented API surface. There is no described filter hook, no settings page reference, no REST route table. If you need to theme the chat, restrict it to logged-in users, or log prompts for compliance, the README does not tell you where to start. You would be reading the PHP source to find out, which is a reasonable thing to do before putting a chat interface on a public page.
The Licence Conflict Is the Loudest Thing in the Repository
The root LICENSE contains the Apache 2.0 text. The README carries a GPL v2 badge, states that Ptero is licensed under GPL v2 or later, and links to the GNU GPL v2 text. Those are not the same licence and they are not interchangeable. Apache-2.0 is permissive and includes an explicit patent grant; GPL v2 is copyleft and requires derivative works distributed to others to carry the same licence. For someone evaluating the project, the practical difference is large. The WordPress plugin header also names GPL-2.0-or-later, so the relevant terms for a particular file or distribution require clarification. This is not a subtle documentation nit. It is the single fact that determines what you may legally do with the code, and the repository contradicts itself on it. Treat the conflicting notices as unresolved for your intended use and ask the maintainer to clarify which terms apply to the files you plan to use.
Where Ptero Breaks Down
The no-server-history design is a privacy feature and an operational limitation at the same time. Teams that need a shared conversation log, a compliance record, or the ability to hand a thread to a colleague cannot get any of that from browser local storage. The moment two people need to see the same conversation, Ptero is the wrong tool. There is a second limitation in the model roster. The README names DeepSeek V4, Llama 3.3, Qwen, MiniMax, and Mistral, but it does not describe how the routing layer selects an upstream endpoint, what happens when a provider is rate limited or down, or whether there is any fallback. A multi-model chat wrapper is only as reliable as its least reliable upstream, and the README gives no failure behaviour. Third, the WordPress integration is the only documented deployment target. If your site runs Drupal, Rails, or a static generator, the README offers you nothing beyond the hosted instance. Fourth, the README asks readers to star the project and points to a Discord server, but it does not describe a release process or versioning scheme, and the repository has no published GitHub releases. That makes upgrade planning guesswork.
Compared With a Self-Hosted Gateway Like LibreChat
The obvious alternative for this problem space is a self-hosted multi-model gateway such as LibreChat, which also puts several providers behind one interface. The difference is where state and control live. LibreChat is built around server-side conversation history and user accounts, with a database behind it, so teams get shared threads, per-user isolation, and an audit trail. Ptero's README describes browser-local history, but this alone does not prove that prompts are never retained by application servers, network intermediaries or upstream providers. Review the actual deployment and their policies before using it for sensitive prompts. If your requirement is 'I need to know what was asked last Tuesday,' Ptero cannot answer and LibreChat can. The second axis is deployment weight. Ptero's documented self-hosted path is a WordPress plugin and a shortcode, which is a lower barrier than standing up a Node application with a database. The trade is that you inherit WordPress's plugin model and its update cycle, and you get no control plane of your own.
Maintenance Cost and the Moving Parts You Do Not Control
The code in this repository is small: PHP glue, JavaScript UI, CSS. That part is cheap to maintain. The expensive part is everything it depends on. Model providers deprecate endpoints and rename model identifiers on their own schedules, and the README's model list (DeepSeek V4, Llama 3.3, and the rest) is a snapshot that will drift. Every upstream change is a potential break in the routing layer, and the README does not describe a configuration file, an environment variable, or a settings screen where model identifiers can be updated. If those are hardcoded in the PHP, each provider change becomes a code edit and a redeploy. That is the real ongoing cost of a wrapper project, and it is not visible from the feature list. On the funding side, the README thanks named sponsors and states there are no paid plans, which means the hosted instance at ptero.pro depends on sponsorship rather than revenue. Self-hosting insulates you from that particular risk, but only if you have resolved the licence question first.
Editorial conclusion
Adopt Ptero if you want a ready-made chat interface you can drop into a WordPress page with the [mlp_ai_chat] shortcode, or a small PHP and JavaScript front end you can read end to end before trusting it with prompts. Do not adopt it if you need per-user history, server-side audit trails, or any control over which upstream model actually answers. Verify three things first: the effective licence, since the repository says Apache-2.0 and the README says GPL v2 or later; where the upstream provider credentials live and who pays for the tokens; and whether the WordPress plugin bundle in the repository is the same code as the one on ptero.pro.
Frequently asked questions
What does the Ptero repository actually contain?
Five files at the top level: CODE_OF_CONDUCT.md, LICENSE, README.md, ai-logic.php and ptero-ai-chat.php. The two PHP files are described as the WordPress integration, and the README's end-user steps point at the hosted site ptero.pro instead.
Which AI models does Ptero list as integrations?
DeepSeek V4, Llama 3.3, Qwen, minimax and Mistral appear in both the feature list and the technology stack section. No endpoints, quotas or rate limits are given for any of them, and the project says access is free with no paid plans or subscriptions.
How do you install Ptero on a WordPress site?
The documented path is manual: download the plugin from the repository, upload it to the site, activate it, then place the [mlp_ai_chat] shortcode on a page or post. No shell command, archive location, WordPress version requirement or shortcode attribute is given.
Which license is Ptero released under?
The repository root LICENSE contains the Apache 2.0 text, while the plugin file header and README identify GPL-2.0-or-later. The project has conflicting licence signals; check the terms applicable to the exact files and seek clarification from the maintainer before relying on a particular interpretation.
Does Ptero keep chat history on its servers?
The README says conversation history is stored locally in the browser and not saved on the project’s servers. That statement does not by itself establish the logging or retention practices of upstream model providers, proxies or a self-hosted WordPress deployment; check each relevant privacy policy and configuration.
Does using Ptero require an account or payment?
The end-user steps list visiting ptero.pro, choosing a display name, selecting a model from a dropdown and chatting, with no account and no payment required. The project calls itself non-profit and says it offers no paid plans or subscriptions.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/aminkheddache-dotcom-ptero)Star history chart for your README
[](https://hysenlabs.com/projects/aminkheddache-dotcom-ptero)Was this useful?