jurieo/chatgpt-share-web: a self-hosted AI account-sharing and resale platform

What chatgpt-share-web actually is

Strip away the feature list and the repository is a web application that lets many people share a small number of upstream AI accounts. The README describes it as a complete restoration of the ChatGPT, Claude, Midjourney, Grok and Gemini sites, plus mirrors of Claude Code and Codex, wrapped in a user system and a monetisation system. The monetisation half is not an afterthought: registration, login, promotion, commission, withdrawal, purchase and usage are listed as one chain, and the README says the operator can be a hands-off manager.

The intended user is therefore not an individual developer. It is someone running a resale or sharing site, typically on an overseas VPS, who needs accounts, plans, quotas and payments handled for them. The README also says the ChatGPT part requires a gateway to work at all, which tells you the project depends on infrastructure the repository does not ship.

The car pool model behind account sharing

The central mechanism is the car, the project's term for an upstream account. Users do not hold credentials; they board a car. The README lists automatic switching to a valid and least-busy car when one expires, chat history synced to the left panel, and clicking a history entry to move the user to the right car. Cross-car chat is supported so a conversation survives the original account owner deleting it.

Account types gate access. The README gives the example of assigning a user a plus car: if that user is not plus, the car cannot be used. Batch creation of plus accounts and batch generation of users are both listed, with user validity counted from first login rather than creation, which the README frames as lowering the registration barrier for reselling accounts directly.

Everything is configured from an admin panel rather than files. The README names the groups: basic, advanced, email, payment, promotion, and gateway and authorisation. Data import and export is offered for account management, user management, subscription management and redemption codes.

Installing it and reaching the admin panel

The README gives one deployment path, a shell script that pulls and runs the Docker image jurieo/gpt-share-server. The script is fetched from the deploy branch, not main, so it can differ from what you see in the repository's default branch. The README notes that new features may not be pushed to GitHub promptly and that the one-click script is how you get the latest system, and that the script deploys through Docker without polluting the host.

curl -sSfL https://raw.githubusercontent.com/jurieo/chatgpt-share-web/deploy/quick-install.sh -o share-quick-install.sh && bash share-quick-install.sh

After the script finishes, the README says to wait for the database to be created and configured, then visit the site. The admin panel is at port 38300 on the /shareadmin path, with the default credentials admin and 123456, and the README instructs you to change the password immediately.

http://ip:38300/shareadmin

The next step the README describes is creating a user, marking that user as an administrator, and using that account on the front end to generate redemption codes and review withdrawals. Personalisation happens under the workbench system configuration section. Server requirements are stated plainly: an overseas VPS, at least 2 cores and 2 GB of memory for stable operation, with stronger hardware suggested once you pass roughly 50 users.

Where the design fights back

The gateway dependency is the largest one. The README states that ChatGPT needs a gateway to work normally, but it does not document how to build or obtain one. Everything about the ChatGPT experience, which is the headline feature, sits behind an undocumented external component. If that component breaks or its terms change, the platform's main selling point goes with it.

The second constraint is the account model itself. Sharing upstream accounts means the operator is exposed to whatever the upstream provider does about concurrent sessions, and the README's own answer is operational: multi-device login can be forbidden, cars fail over, history is backed up so it stays readable after a failure but cannot continue the conversation. That is a workaround, not a guarantee.

Third, the documentation is thin where an operator needs it most. There are no retrieved releases, the licence is not stated anywhere in the repository, and the README does not document rollback, backup restoration or upgrade procedure for the application itself. The one-click script is the only supported install path described, and the README points to a paid deployment service at 400 yuan per session, which suggests the maintainer expects the script alone to be insufficient for some users. The last push to the repository was on 2026-06-24, so treat the GitHub tree as a snapshot rather than the current state of the product.

How it differs from one-api and new-api gateways

The obvious comparison is with API gateway projects such as oneapi and newapi, which the README lists as third-party APIs the platform can connect to. Those projects expose model endpoints behind a key, and their users are developers integrating an API into their own software. chatgpt-share-web points the other way: it consumes gateways and presents a consumer-facing website with plans, cars, redemption codes, commissions and withdrawals.

That difference matters for evaluation. A gateway is judged on protocol compatibility and routing. This project is judged on whether the storefront, the user lifecycle and the payment flow hold together, and on whether the upstream accounts stay alive. The README also mentions a card-issuing address that users can buy from on the front end, which is a commerce concern no API gateway has.

Licence, maintenance and upgrade cost

The repository does not state a licence, and no releases were retrieved, so there is no versioned upgrade path to reason about. The README says the project is for learning and research only and disclaims responsibility for losses, while also advertising paid deployment, affiliate VPS links and a WeChat contact for cooperation. Those two positions sit awkwardly together, and anyone deploying commercially should read the disclaimer as the maintainer's stated position rather than as legal cover.

The README also carries a compliance note: users must follow OpenAI's terms of use and applicable law, and it cites China's interim measures on generative AI services, asking operators not to offer unregistered generative AI services to the public in China. That is a statement of the project's own expectation, not legal advice, and the practical implication is that the operator, not the repository, carries the risk of how the service is offered.

Upgrade cost is mostly operational. The README says features land in the Docker image before GitHub, so pulling a new image is the update mechanism you would be tracking, and there is no documented rollback if one goes wrong.

Themes, logins and the parts that are genuinely built out

Credit where it is due: the surrounding system is more complete than most projects in this category. Login supports username and password plus one-click options for LinuxDo, GitHub, WeChat and Google. Email registration covers verification, password reset and withdrawal. Payment goes through 易支付, with the README suggesting it as a relay for other methods. Redemption codes can be limited by amount, frequency, account type and time window.

Three themes ship: pastel, pop and classic, with the README warning that classic no longer receives new features, which is a quiet signal about where maintenance attention goes. Sensitive-word filtering ships with over a thousand built-in entries and is configurable. Scripts can be injected into the front end for support chat or analytics. None of this changes the core judgement, but it explains why operators choose this over assembling the pieces themselves.

Editorial conclusion

Adopt it only if you intend to run a paid shared-access service and accept that the gateway dependency, the 2-core/2 GB floor and the legal note in the README are all part of the deal. Do not adopt it if you want a normal application to call model APIs under your own keys, or if you need a documented licence, since the repository does not state one. Verify first that your ChatGPT gateway is working, that you have changed the default admin password at http://ip:38300/shareadmin, and that you can live with a codebase whose README says new features may not reach GitHub promptly.

Frequently asked questions

Official sources

1. Issues
2. jurieo/chatgpt-share-web on GitHub
3. Project website
4. README