What Is RegPlatform?
RegPlatform is a batch account registration platform built by xiaolajiaoyyds for automating multi-platform account creation on OpenAI, Grok, Kiro, and Gemini. It handles full OAuth token acquisition, points systems, and multi-user management via Go backend and Vue frontend. RegPlatform is one of the best DevOps Automation tools for AI operations teams scaling bulk accounts, with 417 GitHub stars and 221 forks as of October 2024.
Quick Overview
| Attribute | Details |
|---|---|
| Type | DevOps Automation |
| Best For | AI operations teams scaling bulk accounts |
| Language/Stack | Go 1.25 / Gin / GORM / PostgreSQL / Vue 3 / Vite / Pinia / TailwindCSS |
| License | MIT |
| GitHub Stars | 417 as of Oct 2024 |
| Pricing | Open-Source |
| Last Release | N/A — latest commit 1729e66 on recent date |
Who Should Use RegPlatform?
- AI ops engineers running high-volume account farms for API rate limits exceeding 10k requests per minute across OpenAI and Grok.
- Multi-user SaaS builders needing self-serve registration dashboards with PostgreSQL-backed user/task tracking.
- HuggingFace Space operators deploying worker pools for Turnstile solving and AWS Builder ID registration.
- Cloudflare Workers users routing platform-specific tasks to dedicated node pools like HFNP for OpenAI.
Not ideal for:
- Developers needing one-off registrations without Docker Compose orchestration.
- Teams avoiding complex setups requiring HF tokens, GitHub secrets, and CF keys.
- Beginners lacking Go/Vue deployment experience, as configuration demands AI-assisted adaptation.
Key Features of RegPlatform
- TaskEngine scheduler — Manages elastic worker pools via gRPC calls to Cloudflare-routed HuggingFace Spaces, handling 100+ concurrent registrations per pool.
- HFSpaceService — Performs health checks on HF Spaces (HFNP, HFGS, HFKR, HFTS), auto-scales nodes, and syncs routes in Cloudflare Workers.
- WebSocket real-time logs — Streams filtered completion/error logs from workers to Vue dashboard, reducing latency to under 500ms for task monitoring.
- Multi-platform workers — Dedicated binaries for OpenAI (HFNP), Grok (HFGS), Kiro (HFKR via aws-builder-id-reg), and Turnstile solving (HFTS).
- JWT middleware stack — Enforces auth, CORS, and rate limiting on Gin routes, integrated with GORM models for users, tasks, results, and points.
- OAuth token extraction — Automates post-registration flows skipping 'about-you' steps, redirecting directly to consent for token capture.
- Docker Compose deployment — Supports prod (docker-compose.prod.yml) and dev setups with PostgreSQL persistence and GHCR image pushes.
RegPlatform vs Alternatives
| Tool | Best For | Key Differentiator | Pricing |
|---|---|---|---|
| RegPlatform | AI ops bulk registration | Elastic HF Spaces + CF routing for multi-platform | Open-Source |
| Playwright | Browser automation scripts | Headless Chromium control, no infra needed | Open-Source |
| Puppeteer | Node.js scraping | Google-backed, simple JS API for single sessions | Open-Source |
| Selenium | Cross-browser testing | Java/Python bindings, Grid for parallelism | Open-Source |
Playwright suits script-based automation where you control one browser instance per account, avoiding RegPlatform's distributed worker complexity. Pick Puppeteer for lightweight Node environments without PostgreSQL or Vue overhead. Selenium fits Java-heavy stacks needing legacy browser support, but lacks RegPlatform's SaaS-ready dashboard. For broader DevOps workflows, pair with djevops or browse all DevOps Automation tools.
How RegPlatform Works
RegPlatform centers on a Go-based TaskEngine that dispatches registration tasks to platform-specific workers via Cloudflare Workers acting as path-prefix routers. User requests hit the Vue SPA through Nginx on port 443, proxying API calls to Gin backend on :8000. Backend services use GORM with PostgreSQL for models covering users, tasks, results, points, and Space statuses. HFSpaceService monitors worker health, triggering GitHub Actions for deployments to GHCR and HF Spaces.
Cloudflare Workers route POST requests: /openai/* to HFNP pool, /grok/* to HFGS, /kiro/* to HFKR, /ts/* to HFTS for Turnstile. Workers run dedicated Go binaries (e.g., cmd/openai-worker) implementing platform logic like OAuth flows and token grabs. WebSocket pushes filtered logs (completions/errors only) from PostgreSQL events.
# Clone and setup
git clone https://github.com/xiaolajiaoyyds/regplatformm
cd regplatformm
cp .env.example .env
# Edit .env: HF_TOKEN, GITHUB_TOKEN, CF_KEY, DB creds
docker-compose up -d
# Access dashboard at http://localhost:80
This starts PostgreSQL, Go server, Vue SPA, and mounts volumes for persistence. Initial login creates admin user; configure HF Spaces via dashboard for worker pools. Expect ~2-5 minutes for full stack readiness, with logs streaming on task submission.
Pros and Cons of RegPlatform
Pros:
- Scales to thousands of accounts via elastic HF Spaces without fixed server costs, auto-scaling on demand.
- Platform-specific routing isolates failures, e.g., Grok downtime doesn't block OpenAI tasks.
- Built-in points system tracks registrations in PostgreSQL, enabling multi-tenant billing at 1ms query latency.
- Real-time WebSocket logs filter noise, showing only completions/errors for ops monitoring.
- MIT-licensed with full Docker Compose, deployable on single VPS or Kubernetes with zero code changes.
- Integrates Viper config for secrets, supporting env vars across GH Actions and CF Workers.
Cons:
- Deployment requires HF account, GitHub secrets, and CF Workers setup, adding 30-60 minutes initial config.
- No built-in proxy rotation; pair with external services for IP diversity in bulk ops.
- Worker binaries platform-locked to HF Spaces, limiting on-prem deploys without adaptation.
- Vue dashboard lacks mobile responsiveness, optimized for desktop ops screens.
- GORM migrations manual via Makefile, no auto-apply on docker-compose up.
Getting Started with RegPlatform
Start by cloning the repo and preparing secrets. Edit .env with your HuggingFace token for Space deploys, GitHub token for GHCR pushes, Cloudflare API key for Worker syncs, and PostgreSQL creds.
# Prerequisites: Docker, Docker Compose, make
git clone https://github.com/xiaolajiaoyyds/regplatformm.git
cd regplatformm
cp .env.example .env
# Set HF_TOKEN=your_hf_token, GITHUB_TOKEN=ghp_xxx, CLOUDFLARE_API_TOKEN=xxx
# Deploy HF Space templates: HFNP, HFGS etc. via dashboard later
docker-compose up --build -d
make migrate # Run GORM migrations
Docker Compose launches Nginx (SPA proxy), Go server (:8000), PostgreSQL, and volumes. Access http://localhost:80; register admin account. Submit test task to /openai pool — monitor WebSocket logs for completion. Configure Cloudflare Worker routes post-deploy via HFSpaceService. Initial setup handles 10-50 tasks/minute; scale by duplicating HF Spaces.
Verdict
RegPlatform is the strongest option for AI ops teams automating bulk registrations on OpenAI/Grok/Kiro when running distributed workers beats local scripts. Its Cloudflare-routed HF Spaces deliver isolation and elasticity at zero marginal cost. Caveat: skip if avoiding multi-key configs; otherwise, deploy for production-scale account farming.



