Translation · head to head
wxrks vs POEditor

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
- -

POEditor
Translation
Localisation management billed by string count with unlimited contributors
- From
- Free
- Rated
- -
The short version
- 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.; POEditor the quota counts every string on the account, including obsolete terms from retired features, so cost creeps upward unless someone deliberately prunes projects.
- They diverge on capability: wxrks covers Published price ladder, POEditor covers String based billing.
- Prices and features above were last checked on 31 August 2026.
Where they differ
Only the attributes on which wxrks and POEditor actually diverge.
Identical on both: starting price (Free), free tier (Yes), 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 POEditor
- String based billing
- Format coverage
- Translation memory
- API and webhooks
- Machine translation
- Contributor roles
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 POEditor
- Content operations with many occasional reviewers, since seats are unlimited and only analytics users are chargednot POEditor
- Developer-led localisation pulling strings from GitHub, GitLab or Bitbucket rather than a content management systemnot POEditor
- Small teams and side projects that can live inside 60,000 words a year on the permanent free tiernot POEditor
POEditor
- Software with many target languages and a volunteer or community translator poolnot wxrks
- Development teams that want new strings pushed from continuous integration and translations pulled back automaticallynot wxrks
- Small companies that cannot justify per seat pricing for translators who work occasionallynot wxrks
- Open source projects that qualify for the free plan and need real workflow rather than a spreadsheetnot 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.
POEditor
- The quota counts every string on the account, including obsolete terms from retired features, so cost creeps upward unless someone deliberately prunes projects.
- Several projects share one account quota, so a team can be pushed into a higher tier by work in an unrelated repository.
- There is no in-context or visual editor, so translators guess at where a string appears and length or gender errors surface only after a build.
- Quality assurance checks are basic compared with the larger platforms, with no configurable rule sets or enforced terminology gates.
- The company is small, support is email based, and there is no self-hosted or on-premises option, which rules it out where data residency is contractually fixed.
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
POEditor
Free- FreeFree
- Around 1000 strings
- Unlimited contributors and languages
- Open source projects can apply for a free plan
- Start$14.99/month
- Higher string quota
- API access
- Translation memory
- Plus$29.99/month
- Larger string quota
- Repository integrations
- Webhooks
- Premium$59.99/month
- Large string quota across all projects
- Priority support
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.
Choose POEditor if
- You need string based billing.
- You want to start without paying.
- You also want format coverage.
Questions people ask
- Is wxrks or POEditor better?
- Neither clearly leads. wxrks starts at Free and POEditor at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, wxrks or POEditor?
- wxrks starts at Free and POEditor at Free.
- Does wxrks or POEditor run on more platforms?
- wxrks runs on Web, API. POEditor runs on Web.
- Can I use wxrks for free?
- Both have a free tier, so you can try either at no cost before committing.
- 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 POEditor is typically brought in for.
- What can wxrks do that POEditor cannot?
- wxrks covers Published price ladder, Unlimited user seats, Four parallel meters, Published overage rates. POEditor covers String based billing, Format coverage, Translation memory, API and webhooks.
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.
POEditor: Does it charge per translator?
No. Contributors and languages are unlimited on every plan. Only the total string count is billed.
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.
POEditor: Is there a free plan for open source?
Yes, open source projects can apply for a free plan, which is why many community translated applications use it.
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.
POEditor: Does it support in-context translation?
No. Translators work from the string list and any comments or screenshots you attach, not from a live preview.
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 Plunet
- wxrks vs Sonix
- wxrks vs Twine
- wxrks vs Unbabel
- wxrks vs Weglot
- wxrks vs Lokalise
- wxrks vs Transifex
- wxrks vs Pontoon
- wxrks vs SDL Trados Studio
- POEditor vs Crowdin
- POEditor vs memoQ
- POEditor vs Phrase
- POEditor vs XTRF
- POEditor vs XTM Cloud
- POEditor vs Localazy
- POEditor vs Smartling
- POEditor vs Wordbee
- POEditor vs Smartcat
- POEditor vs Plunet
- POEditor vs Sonix
- POEditor vs Twine
- POEditor vs Unbabel
- POEditor vs Weglot
- POEditor vs Lokalise
- POEditor vs Transifex
- POEditor vs Pontoon
- POEditor vs SDL Trados Studio
