This project has been archived by its maintainers, and is no longer receiving any updates.
llamka
MLOps for building second brain
There is few principles we want to build llamka around
| Principle | Because |
|---|---|
| Standardize interface for different model vendors | Ability to substitute and store conversations uniformly |
| Automation of pipelines | Consistency |
| Maintain teargeted conversation datasets | Capture requirements and provide data for finetuining and evaluation |
| Model evaluation and management | Informed decision making about trade off between open and closed models |
| Preference to open weight models and self hosting | Ability to finetune, privacy and lower cost |
Architecture
-
llore - (llamka-core) Tornado App that keep everything running. llore provides api and all other services built on top of it
- MVP
- provide abstraction interface over LLM providers (local: ollama; remote: openai, claude;)
- maintain external document locations/versions and rebuild vector db collections on changes
- augmentation pipelines and chatbot config
- completion api to interact with configured models and chatbots
- later
- store chatbot interactions in oumi conversation format per user if instructed
- maintain chatbot library (includes: system prompt, finetuning and augmentation pipelines, data dependencies, and build schedule)
- maintain conversation datasets and use them for tuning, RAG and testing
- schedule and run pipelines: finetuning, RAG, chatbot evaluation
- monitor and run services: databases, queues, proxies, ui (llit)
- MVP
-
llit - streamlit UI
- MVP
- Chatbot interaction
- later
- Inspect previous conversations or from library
- Inspect data: sql, document db, vector db
- Inspect logs from pipelines
- Configuration: models, chatbot, pipelines
- MVP
Got API and streamlit endpoints working, almost MVP!!!
Project Docs
For how to install uv and Python, see installation.md.
For development workflows, see development.md.
For instructions on publishing to PyPI, see publishing.md.
This project was built from simple-modern-uv.
1 maintainer
Metadata
1 maintainer
Release files for llamka 0.0.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| llamka-0.0.5.tar.gz | 27.3 MB | With provenance | Details for llamka-0.0.5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| llamka-0.0.5-py3-none-any.whl | Python 3 | none | any | Details for llamka-0.0.5-py3-none-any.whl |
Total release size: 27.3 MB
Release files / llamka-0.0.5.tar.gz
| Download URL | llamka-0.0.5.tar.gz |
|---|---|
| Size | 27.3 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a5fb907ff023265287679dd33c0e4c392eafd8a9a1fb1bb29be710b3dcf27443
|
|
BLAKE2b-256 checksum How to use checksums |
9d181368ccbfdaf89674b9c5a56255815d3643f5380da7e39e67902942c0c4f0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 13, 2025.
Transparency logRelease files / llamka-0.0.5-py3-none-any.whl
| Download URL | llamka-0.0.5-py3-none-any.whl |
|---|---|
| Size | 29.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
908886d6aaea8c7437eb3ac10204ede2c692d3d0eeb8360f8a6d6ccdc25e211f
|
|
BLAKE2b-256 checksum How to use checksums |
22a52ad58467aa73cdeefaa1221fd58cee48cdd9f8e1fb4363437b4bb179f44b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 13, 2025.
Transparency logSecurity for llamka 0.0.5
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for llamka-0.0.5.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 13, 2025.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
