Celery
This entry runs no foundation model. Every finding below is quoted to the vendor’s own document, or marked not disclosed where the vendor publishes nothing.
Distributed task queue for Python. Runs work asynchronously across worker processes, with scheduling, retries and result backends.
No foundation model. Celery does not run one, so there is no model provenance to record. Distributed task queue for processing messages and scheduling background jobs; the official docs describe it as a distributed system to process vast amounts of messages with focus on real-time processing, with no foundation model, inference, or AI feature anywhere in the documented feature set. Reviewed from the vendor’s own documentation: docs.celeryq.dev ↗ If that is out of date, tell us at right of reply.
Not yet assessed. We publish a sovereignty position only where the vendor documents one — we do not infer it from a domain or a company name.
Vannus records, from the vendor's own published documents, the legal entity a customer contracts with, the country that entity sits in, and the governing law of its terms — and whether the vendor runs its own model or resells someone else's. Each finding is quoted to its source and dated, or marked not disclosed where the vendor publishes nothing. No paid placement on a record, in the catalog or in search — affiliate status is walled off from the record, enforced by a test in the build. See the methodology →
Work here and think we got something wrong? Corrections and right of reply → — free, no account, and we publish your response next to our entry.