Translation · head to head
wxrks vs Plunet

wxrks
Translation
Translation platform formerly called Bureau Works, priced by processed words per year with unlimited seats and a real free tier
- From
- Free
- Rated
- -

Plunet
Translation
Business and translation management system for language service providers and in-house translation departments
- From
- On request
- Rated
- -
The short version
- Only wxrks has a free tier, so it costs nothing to try first.
- Each has a real cost: wxrks connectors are marked as billed separately on the pricing page with no rate published anywhere, so the integration that justifies buying the platform carries a cost you cannot discover until you ask.; Plunet pricing is never published and licensing is per user, so a growing agency faces a recurring negotiation each time it adds project managers.
- They diverge on capability: wxrks covers Published price ladder, Plunet covers CAT tool connectors.
- Prices and features above were last checked on 1 September 2026.
Where they differ
Only the attributes on which wxrks and Plunet actually diverge.
Identical on both: user rating (Not yet rated), category (Translation).
What each one covers
Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.
Only in wxrks
- Published price ladder
- Unlimited user seats
- Four parallel meters
- Published overage rates
- Marketplace
- Repository and design connectors
Only in Plunet
- CAT tool connectors
- Automated pricing
- Vendor and resource management
- Workflow templates
- Financial reporting
- Client and vendor portals
What people use each for
The jobs each tool is most often brought in to do.
wxrks
- A team that needs to model localisation cost from published numbers rather than sit through a sales cycle to get a figurenot Plunet
- Content operations with many occasional reviewers, since seats are unlimited and only analytics users are chargednot Plunet
- Developer-led localisation pulling strings from GitHub, GitLab or Bitbucket rather than a content management systemnot Plunet
- Small teams and side projects that can live inside 60,000 words a year on the permanent free tiernot Plunet
Plunet
- A translation agency running dozens of concurrent projects across freelance vendors that needs automated quoting from CAT analysesnot wxrks
- A corporate localisation department wanting margin and vendor-cost visibility across internal and outsourced worknot wxrks
- An LSP replacing spreadsheet-based project tracking that is causing missed deadlines and billing disputesnot wxrks
- An agency needing client and vendor self-service portals to cut manual email coordinationnot wxrks
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
wxrks
- Connectors are marked as billed separately on the pricing page with no rate published anywhere, so the integration that justifies buying the platform carries a cost you cannot discover until you ask.
- Four separate meters run in parallel and any one of them can be exhausted while the others have headroom, so a workload heavy on API calls or AI tokens can force a plan upgrade long before the word allowance is touched.
- Word allowances are annual rather than monthly, so a single large launch early in the term can consume most of the year and leave the remaining months on overage rates.
- The marketplace is promoted as a way to reach agencies and translators, but whether the vendor takes a commission and how linguists are paid is not disclosed anywhere on the public site.
- The company rebranded from Bureau Works in March 2026, so existing documentation, third-party guides, integration listings and internal references still carry the old name, and the vendor is small with no disclosed funding behind it.
Plunet
- Pricing is never published and licensing is per user, so a growing agency faces a recurring negotiation each time it adds project managers.
- Configuration to match an agency real workflow is substantial, and firms report months of setup before the system reflects how they actually work.
- It manages the business layer only; you still need and pay for separate CAT tools, so total software spend is higher than the Plunet quote alone suggests.
- The interface is dense and built for full-time project managers, which makes it a poor fit for occasional users or very small teams.
- Reporting and dashboards are functional rather than modern, and firms wanting BI-grade analytics typically export data to a separate tool.
Pricing, plan by plan
wxrks
Free- FreeFree
- 60,000 processed words per year
- 2,300 API calls
- 300,000 stateless AI tokens
- Starter$38/month
- Billed yearly
- 1 million words per year
- 38,000 API calls, 5 million AI tokens, 330,000 MT words
- Boutique$180/month
- Billed yearly
- 3.2 million words per year
- 122,000 API calls, 16 million AI tokens, 1 million MT words
- Clockwork$470/month
- Billed yearly
- 9.6 million words per year
- Overage at 0.0005 USD per word
Plunet
On request- Plunet BusinessManager$undefined/year
- Licensed per named or concurrent user
- Implementation and configuration charged separately
- Pricing not published, quote depends on user count and modules
Which should you pick?
Choose wxrks if
- You need published price ladder.
- You want to start without paying.
- You work on Web, API.
- You also want unlimited user seats.
Questions people ask
- Is wxrks or Plunet better?
- Neither clearly leads. wxrks starts at Free and Plunet at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, wxrks or Plunet?
- wxrks has a free tier; the other does not. Paid plans start at Free for wxrks and On request for Plunet.
- Does wxrks or Plunet run on more platforms?
- wxrks runs on Web, API. Plunet runs on Web.
- Can I use wxrks for free?
- Yes. wxrks has a free tier, so you can try it without paying. Plunet starts at On request.
- What is wxrks best used for?
- wxrks is most often used for a team that needs to model localisation cost from published numbers rather than sit through a sales cycle to get a figure, content operations with many occasional reviewers, since seats are unlimited and only analytics users are charged, developer-led localisation pulling strings from github, gitlab or bitbucket rather than a content management system, small teams and side projects that can live inside 60,000 words a year on the permanent free tier. Of those, a team that needs to model localisation cost from published numbers rather than sit through a sales cycle to get a figure and content operations with many occasional reviewers, since seats are unlimited and only analytics users are charged are not what Plunet is typically brought in for.
- What can wxrks do that Plunet cannot?
- wxrks covers Published price ladder, Unlimited user seats, Four parallel meters, Published overage rates. Plunet covers CAT tool connectors, Automated pricing, Vendor and resource management, Workflow templates.
Answered from the vendors’ own pages
wxrks: Is this still Bureau Works?
Yes. The company rebranded to wxrks on 23 March 2026 and bureauworks.com redirects to wxrks.com. The legal entity is Bureau Translations Inc.
Plunet: Does Plunet translate documents?
No. It manages quoting, workflow, vendor assignment and billing around translation work performed in separate CAT tools.
wxrks: Is the free plan permanent?
Yes. It allows 60,000 processed words a year along with API call, AI token and machine translation allowances, and unlimited user seats. A fourteen day trial of paid features is offered separately.
Plunet: Is pricing public?
No. Plunet is sold on a quote basis licensed per user, and cost depends on user count and modules selected.
wxrks: What happens when I exceed the word allowance?
You pay a published per-word overage rate, from 0.0009 USD on Starter falling to 0.0003 USD on the largest plans, rather than being cut off.
Plunet: Who actually buys it?
Translation and localisation agencies and corporate in-house translation departments, not the companies commissioning a one-off translation.
wxrks: Do connectors cost extra?
The pricing page states connectors are billed separately but publishes no rate. Get the figure in writing before signing, because it is the one unbounded item in an otherwise transparent price list.
Related pages
Other head to heads
- wxrks vs Crowdin
- wxrks vs memoQ
- wxrks vs Phrase
- wxrks vs XTRF
- wxrks vs XTM Cloud
- wxrks vs Localazy
- wxrks vs Smartling
- wxrks vs Wordbee
- wxrks vs Smartcat
- wxrks vs POEditor
- wxrks vs Sonix
- wxrks vs Twine
- wxrks vs Unbabel
- wxrks vs Weglot
- wxrks vs Pontoon
- wxrks vs SDL Trados Studio
- wxrks vs Reverso
- Plunet vs Crowdin
- Plunet vs memoQ
- Plunet vs Phrase
- Plunet vs XTRF
- Plunet vs XTM Cloud
- Plunet vs Localazy
- Plunet vs Smartling
- Plunet vs Wordbee
- Plunet vs Smartcat
- Plunet vs POEditor
- Plunet vs Sonix
- Plunet vs Twine
- Plunet vs Unbabel
- Plunet vs Weglot
- Plunet vs Pontoon
- Plunet vs SDL Trados Studio
- Plunet vs Reverso
