Hi — I'm Aveer. I build practical tools for self-hosting, automation, and local AI orchestration. My work focuses on clean Python backends, lightweight frontends, and small utilities that solve everyday problems — from running local LLM stacks to system-level automation and performance tweaks.
-
LM-Nexus — AI-tools for self hosting (privae for now) A local AI control center with a Python FastAPI backend and a Vue.js frontend. Designed to manage llama.cpp / Llama-swap, Docker and Edge apps for running models locally. Tech mix: Python, Vue, CSS, JavaScript, PowerShell, TypeScript.
Notes: focuses on reproducible local model hosting and tooling for self-hosted AI workflows.
-
OpenZeus — Shell automation toolkit
Collection of shell utilities and scripts for automation and system tasks. Small, efficient, and focused on cross-environment sysadmin workflows. -
The-Settlers-7-CPU-Optimizer — Game performance utility (legacy) Python utility that adjusts process affinity and priority for The Settlers 7 to improve framerate (by disabling hyperthreading affinity for the process). Gives a noticeable FPS boost without changing graphics. Languages: Python + small HTML docs.
If you find my work useful, you can buy me a coffee:
- Languages: Python (primary), Shell, JavaScript / Vue
- Tools & frameworks: FastAPI, Uvicorn, Vite, Vue.js, Docker
- Local AI: llama.cpp, Llama-swap, custom orchestration for on-prem models
- Dev workflow: ruff for linting/formatting, pytest for tests, small CLI utilities
- I welcome issues and focused PRs — especially for reproducibility, docs, or small feature additions.
- For LM-Nexus: prefer changes that keep the local-first approach and clear, minimal dependencies.
- If you want to collaborate on a project, open an issue with a short proposal and testing instructions.
- GitHub: https://github.com/Aveer
- Python-first, pragmatic error handling (try/except at boundaries, safe defaults for long-running loops)
- Use dataclasses for structured results, polars for DataFrame work, and numpy for numeric arrays
- Keep functions small; use visual dividers (e.g.,
# ───) and clear naming conventions
Thanks for stopping by — explore the repos above for details. If you'd like, I can:
- Add badges (languages, license, build) and a timeline,
- Create a shorter bio or a developer-focused variant,
- Or generate a README tailored for a specific audience (employers, collaborators, or users).