Skip to content
capzy
solvers
docs
blog
pricing
resources
English
en
sign in
get api key
changelog
what's new at capzy — features, improvements, and fixes.
April 16, 2026
New
Account Settings & Company Field
●
New /dashboard/account page — change email, password, edit profile
●
Company field on registration (optional)
●
Account tier display with concurrent task & rate limits
●
Cloudflare Turnstile CAPTCHA on login & register for bot protection
April 15, 2026
Improved
Billing, Terms & Usage Overhaul
●
Transaction history moved to Usage page with stacked success/failure daily chart
●
Billing page simplified — FAQ, no-refund policy, $1–$10,000 deposit range
●
Terms of Service rewritten: intangible goods, no-refund, chargeback clause
●
Welcome widget on dashboard next to balance card
●
First/last name on registration, shown in welcome widget
●
Multi-language code examples on docs (Python, Node.js, Go, PHP, C#)
April 14, 2026
New
Support Tickets & API Key Tracking
●
Full Zendesk-style support ticket system with staff roles
●
API key tracking — every task records which key was used
●
Per-key usage stats and task history at /dashboard/api-keys/[id]
●
Usage analytics page with per-type breakdown and clickable drill-down
●
Transaction pair merging — failed tasks show as single 'Failed (refunded)' row
April 13, 2026
Improved
Rate Limiting & Solver Performance
●
Per-account concurrent task caps and rate limits (regular/enterprise/admin tiers)
●
MTCaptcha solver burst performance fix — CTC inference moved to ML service
●
Persistent browser contexts — connections stay warm between solves for faster performance
●
Improved task distribution — even load balancing across solver fleet
April 12, 2026
New
New Solver Support
●
CaptchaFox browser solver with shadow-DOM piercing
●
GeeTest v3 slider solver with gap detection
●
MTCaptcha token-based solver via fake page
●
Temu swap puzzle solver with OpenCV piece comparison
April 2026
Infrastructure
Multi-Node Rolling Deploy
●
Graceful solver drain system — zero-downtime deployments
●
Node-by-node rolling updates without service interruption
●
Pod disruption budgets for high availability
●
Infrastructure ready for multi-node horizontal scaling