About

We build the layer under the people who deliver translation.

Agencies and platform vendors are the ones with the client relationship, the terminology and the accountability. What they often lack is a document pipeline that returns a usable file. That is the gap we work in.

What we are

Not an agency, not a TMS, not a translation marketplace.

We build and run a document translation pipeline: files go in, finished documents come out with their layout intact, their terminology enforced and their quality checked before delivery.

We sell that capability to organisations that already deliver translation to somebody else — translation agencies, and the vendors whose products their customers use. We do not compete with them for their clients.

The pipeline is built in-house rather than assembled from third-party services. That matters because the hard part is not translation; it is everything around it, and you cannot fix that part by swapping a vendor.

How we think about the problem

Four positions that shape everything on this site.

  • The file is the unit of work

    Not the segment, not the string. A document has structure and the structure carries meaning, so the pipeline is built around pages and documents rather than text fragments.

  • A model should not grade itself

    The quality check runs on a different model from the one that produced the translation. This is the single design decision that catches the most errors.

  • Say what is not true less often

    No accuracy percentages, no speed claims, no client logos we cannot back up. The numbers on this site are the limits our production system enforces, and nothing else.

  • The awkward file is the real test

    Anyone can translate a clean document. A pipeline is judged on the half-scanned PDF with a table that spans three pages.

Who we work with

Two kinds of organisation, for different reasons.

Translation agencies come to us with a capacity problem: they can sell more work than they can process without adding coordination overhead, and the files that break are the ones that eat their margin.

Platform vendors come with a product problem: their customers keep asking for document translation inside the product, and a raw translation API produces output that embarrasses them.

Both end up in the same place — the document pipeline — but they need different things from it, which is why there are two separate pages for them.

Where the detail lives

Two pages that go deeper than this one does.

About us questions

Do you compete with your customers?

No. We sell to the people who deliver translation, not to their clients. Selling past a partner into their customer base would end the relationship, and we are not interested in that trade.

Do you use third-party translation engines?

The pipeline is built in-house, including the parts that decide how each page is processed and the quality check that runs before delivery.

How big is the team?

Small enough that the people who build the pipeline are the people who answer questions about it. We would rather not publish a headcount than publish one that changes every quarter.

Where are you based?

The operating entity is Boyubo Information Technology Co., Ltd. It is registered in Shenzhen, China. We work across European and Asian business hours and answer in English.

Can we visit or have a call?

Yes. Start with a sample document so the call has something concrete in front of it — that makes the conversation far more useful for both sides.

Send us a real file. See what comes back.

Pick the document that normally causes you the most trouble — the scanned one, the chart-heavy one, the one with the tables. We will run it and send the finished file back so you can judge the layout yourself.

  • No signup, no self-service portal — you send a file, we run it.
  • You get the finished document back, not a screenshot of one.
  • If it is not good enough, you have lost nothing.