Our Latest Features and Improvements

Pricing stops charging by keyword

The free plan no longer runs out. It used to be a 15-day trial wearing the word "Free": on day 16 the account went read-only, which for someone who had not paid yet is the same as deleting it. Now Free is a plan — 1 project, 2 languages, unlimited keys and 500 AI translations a month, with no card and no end date. New accounts still get 15 days with Growth limits; when those end they land on Free instead of hitting a wall.

Translation keys are unlimited on every plan, free included. Charging by keys had three problems: the paid plans differed in nothing else, the cap hit while importing your language file (before anyone had seen the product work), and it punished the best customer — an agency with twenty small apps has few keys and a lot of value. Plans now differ by languages, projects, team members, client workspaces and AI volume, which is the only part that actually costs money.

Studio is the agency plan, not a bigger box: 10 client workspaces kept apart, the white-label review portal, and the invoice split per client. Those features are now part of that plan instead of being open to everyone.

Prices have not changed: Starter €9, Growth €49, Studio €149, Scale €199 a month.

One correction: the pricing table listed "Translation memory" as a feature from Starter upwards. There is no translation memory in AZbox. It is gone from the site until there is.

Teams, clients, client review and quality checks

For everyone:

• Quality report: AZbox now checks your translations against the source language — placeholders that do not match, broken ICU plurals, mismatched HTML, text that will overflow a button, and what is still missing. In the dashboard under Quality, and in CI with azbox qa --fail-on error, which exits non-zero so a broken placeholder stops the deploy.
• Teams and roles: invite people as admin, developer, translator or reviewer. A translator writes translations and nothing else; a reviewer approves or asks for changes. Enforced by the database rules, not just the dashboard.
• Plan limits are now enforced server-side. Keywords, projects, members and languages per project, and the 15-day trial. The counters are kept by the server; they used to live in the dashboard, where they could be edited.

For agencies:

• Clients: group projects by end client, see what each uses, and limit a teammate to the clients they work for.
• Client review portal: send your client a link to approve translations, with your brand and no AZbox anywhere. Approvals land on the keywords, and are marked stale if the text changes afterwards.
• Invoice breakdown by client, with CSV, to re-bill. Stripe still issues one invoice.

Corrections worth naming:

• The endpoint that fetched a website for importing accepted any URL from anyone, which made it usable to reach addresses that are not public. It now requires a dashboard session and only goes out to the internet.
• DeepL translation from the dashboard accepted an account id as its credential. It now requires a dashboard session.
• azbox-cli 0.2.0 speaks English, and adds azbox qa.

Agent skill and a Node.js client that works

New:

• AZbox skill for coding agents: teaches Claude Code, Cursor and other agents how to wire AZbox into Flutter, PHP or CI. Install it as a Claude Code plugin or with npx skills add azbox-io/azbox-skills.
• getTranslations() in azbox-node: returns a { keyword: translation } dictionary directly and leaves out untranslated keys.

Corrections worth naming:

• azbox-node 0.1.0 and 0.1.1 never worked: they called a URL without /v1, sent a parameter the API rejects, and require("azbox-node") pointed to a file missing from the package. 0.2.0 fixes all three, accepts apiKey, and also runs in React Native. Update with npm install azbox-node@latest; the Node.js quickstart is rewritten for it.
• azbox-cli 0.1.0 and 0.1.1 did nothing when installed from npm: they exited without output. Fixed in 0.1.2.

CLI, MCP server and project API keys

New:

• azbox-cli: pull your translations into JSON or ARB files from the command line or from CI. Open source, no dependencies. It only reads: keys are still created in the dashboard.
• MCP server: lets Claude Code, Cursor and other MCP clients read your project — find the key behind a string, list what is untranslated, avoid duplicate keys. Read-only and open source.
• Project API keys, under Settings → API keys: tied to one project, stored hashed, revocable, and showing when each was last used. A key tied to a project cannot read any other.

Corrections worth naming:

• The REST API reference documented a token parameter that the API rejects. The parameter is api_key.

Documentation, per-stack quickstarts and the Studio plan

Documentation:

• Real docs at /docs/, in English and Spanish. Previously this page pulled two marketing articles from the blog, which is not documentation.
• Quickstarts per stack: Flutter, Node.js and PHP. Every snippet comes from the published package, not from memory.
• REST API reference: the endpoint behind all three libraries, documented so React Native, native iOS and Android, Vue, Angular or any other stack can integrate without waiting for an SDK.

New plan:

• Studio, 149 €/month: for agencies and studios delivering for several clients. 10,000 keywords, everything in Growth, one project per client with keys kept separate, and eligibility for the 50% recurring margin of the partner program.

Corrections worth naming:

• The Flutter guide told you to install a package that does not exist on pub.dev. The correct one is azbox.
• The Node guides documented push and pull methods the client does not have. The client reads; keywords are created in the dashboard.
• The Spanish blog was serving its 42 posts on URLs ending in .md, with the clean URL returning 404. Both forms were in the sitemap.

Document Translation with Specialized Contexts

New Features:

You can now translate documents and text into multiple languages with specialized contexts and domains:

• Multiple Languages: Translate your content into the languages you need for your audience.
• Specialized Contexts: Choose the right domain for more accurate, context-aware translations:
  • Legal: Contracts, terms, compliance documents
  • IT: Technical documentation, software strings, APIs
  • Financial: Reports, statements, financial communications
  • Education: Learning materials, courses, academic content
• Better Accuracy: Domain-specific terminology and style improve translation quality for professional and specialized content.

Whether you need to localize a legal agreement, technical docs, or educational material, you can now select the appropriate context so translations match your domain and audience.

PHP library published on Packagist

azbox/azbox-php is available through Composer:

composer require azbox/azbox-php

It takes a different approach from the Dart and Node libraries: instead of handing you the keywords to render yourself, it translates the page and injects a language selector.

• PHP 7.0 or newer, with or without Composer
• Configurable selector: position, dropdown or inline, full language names or codes
• Source and target languages declared at initialisation

Step by step in the PHP quickstart.

Node.js client published on npm

azbox-node is available on npm:

npm install azbox-node

One class, one method, and nothing you have to guess:

const client = new AzboxClient({ token, projectId, language });
const keywords = await client.getKeywords({ afterUpdatedAt });

• Read-only: keywords are created in the dashboard or by importing a file
• Incremental sync: afterUpdatedAt returns only what changed since your last fetch, which is what makes over-the-air updates practical
• Node 18 or newer, using the global fetch

Step by step in the Node.js quickstart.

Improved Billing Experience & Smarter Plan Management

New Features:

We've made significant improvements to how you manage your subscription and billing:

• Easy Invoice Access: Download your invoices directly from your account. All your billing history is now available in one place, making it easier to track expenses and manage your subscription records.

• Smart Plan Recommendations: The upgrade process is now more intuitive. The system automatically shows you the most relevant plan options based on your current subscription, making it easier to find the right plan for your needs.

• Improved Plan Selection: Plans are now organized in a clearer order, helping you understand your upgrade options at a glance. The interface only shows relevant plans, reducing confusion and streamlining your decision-making process.

User Experience Improvements:

• Redesigned Invoice Screen: A completely new invoice management interface with better organization, faster loading, and clearer information display
• Enhanced Payment Flow: Smoothed out the plan upgrade process with better visual feedback and clearer steps
• Better Billing Information Management: Improved forms and validation to make updating your billing details easier and more reliable

Security & Reliability:

• Enhanced Payment Security: Improved payment processing with better verification and duplicate payment prevention
• More Reliable Transactions: Added safeguards to ensure your payments are processed correctly and securely every time

These updates make managing your subscription and accessing your billing information simpler and more straightforward, so you can focus on what matters most: using AZbox to grow your business.

Flutter Plugin Update & Performance Enhancements

New Features:

We're pleased to announce a significant update to our Flutter plugin, bringing enhanced functionality and improved developer experience:

• Updated Flutter Plugin: Latest version with improved compatibility and new features
• Enhanced Caching System: Implemented a more efficient caching mechanism that significantly reduces API calls and improves response times
• Smart Cache Management: Automatic cache invalidation and intelligent refresh strategies
• Improved Error Handling: Better error messages and recovery mechanisms for smoother development workflow

Performance Improvements:

This update includes several performance optimizations that make the plugin faster and more efficient:

• Reduced Memory Footprint: Optimized memory usage for better app performance
• Faster Translation Loading: Improved data fetching and processing speeds
• Optimized Network Requests: Reduced bandwidth usage through better request batching
• Enhanced Background Processing: More efficient handling of translation tasks in the background

Bug Fixes:

We've addressed several critical issues to improve stability and reliability:

• Fixed memory leaks that occurred during long-running translation sessions
• Resolved caching issues that caused stale data to be displayed
• Corrected error handling in network failure scenarios
• Fixed compatibility issues with the latest Flutter SDK versions
• Resolved race conditions in concurrent translation operations
• Fixed UI rendering issues when switching between languages quickly

These improvements ensure a more stable and performant experience for developers using our Flutter plugin, making it easier to integrate and maintain localization in Flutter applications.

New web and panel design

New Features:

We're excited to announce a complete overhaul of our web interface and control panel, bringing you a more intuitive and modern experience:

• Streamlined Dashboard: Redesigned main dashboard for better visibility of key metrics
• Enhanced Navigation: Improved menu structure for easier access to all features
• Modern UI Elements: Updated design components following latest web standards
• Responsive Layout: Better adaptation to all screen sizes and devices
• Performance Improvements: Faster loading times and smoother transitions
• Dark Mode Support: Added system-wide dark mode option
• Accessibility Updates: Improved keyboard navigation and screen reader support

Bug Fixes:

We've resolved several issues related to keyword category assignments