I’m planning to release the current master branch of Argos Translate as 1.10 soon. The biggest change is increased Spacy support. This version will still include Stanza as a dependency but will be the first step in trying to move away from Stanza.
Argos Translate 1.10 should also fix a SentencePiece compatibility issue with Python 3.13.
Testing and feedback on the release is greatly appreciated!
This is awesome! I look forward to test things out 
Great! Can you put the version number somewhere on https://libretranslate.com/ so we can know when we can test it?
On a related note, I’d love to see what the LLM version can do, will you offer a paid plan that allows us to call that API?
Testing would need to be done before we deploy it in production on libretranslate.com.
It would be difficult to offer a hosted LLM version because it’s expensive to run LLMs. The price point would be too high.
How many customers at what price would you need for hosted LTEngine to be profitable? Vast.ai RTX 4090 GPUs are about $0.75/hr or $550/month.
Unless you are a large player with a large datacenter, I don’t think it’s feasible. GPU compute just doesn’t scale well. I think a better monetization model might be to offer a pre-compiled version of LTEngine that you can just run on your machine without needing to compile it.
GPU inference at scale doesn’t scale well and rarely makes sense financially.
However, letting users BYOK and use something like https://openrouter.ai/ is a suitable alternative.
Just warnings, but noticed them when running the latest CLI version:
$ ./venv/bin/argos-translate --from-lang en --to-lang it 'This is a great tool'
warnings.warn(
('Could not load Stanza resources for package Hebrew → English',)
2025-10-24 10:34:36 WARNING: Language he package default expects mwt, which has been added
2025-10-24 10:34:47 WARNING: Unsupported language: eo If trying to add a new language, consider using allow_unknown_language=True
2025-10-24 10:34:55 WARNING: Unsupported language: az If trying to add a new language, consider using allow_unknown_language=True
Translation output is great though, so I don’t think it’s a problem.
We have a fallback for missing languages (eo/az), so those can be ignored.
@argosopentech, I think we can now add back the VI language to argospm. I’ve been running translations for many documents from VI->EN and it works pretty well.
[SOLVED]
build from source [sentencepiece 0.2.0] solve the problem but devs should take attention on that..
trying to use argos-translate with language packs en-bg/bg-en → en-bg works but bg-en not … maybe its important to mention language models are downloaded manually cos via script every time breaks in some part and this is happens only for “bg-en” model .. … trying several ways even with native macos app - same result - even deleting and re-downloading models - with en-bg works but with bg-en app terminates without error… WIll be good to be provided and older argos-language-models versions cos due to i can install older argos-translate verison im not able to install older language pack version where i think is the problem. Also for 1.10 there is problem with “sentencepiece” - via pip (python3.12) installing sentencepiece it installs v.0.2.1 successfully but when i try to install argostranslate it trying to install older version v.0.1.99 and fails even if i try to install manually only that package of that version fails:
the host OS is macos Catalina 10.15.7
here is part of report:
sudo python3 -m pip install “sentencepiece==0.1.99” Collecting sentencepiece==0.1.99 Using cached sentencepiece-0.1.99.tar.gz (2.6 MB) Installing build dependencies … done Getting requirements to build wheel … done Preparing metadata (pyproject.toml) … done Building wheels for collected packages: sentencepiece Building wheel for sentencepiece (pyproject.toml) … error error: subprocess-exited-with-error × Building wheel for sentencepiece (pyproject.toml) did not run successfully. │ exit code: 1 ╰─> [105 lines of output]
I just re-enabled it! People have been asking for Vietnamese for a while.