DeusApps · Developer Tools · Linux/Server Automation · Python CLI/TUI · TypeScript SaaS · 3D Workflow Tools · Unity/C#
deusapps.store · armactl · Deus AI Limits Extension · LinkedIn
I build practical tools, game prototypes, automation systems, SaaS foundations, browser extensions, and 3D workflow utilities.
- 🧩 DeusApps — small developer tools and workflow utilities
- 🧠 AI workflow tools and local-first browser utilities
- 🧭 Chrome extensions for usage tracking and developer productivity
- 🏗️ SketchUp / Blender pipeline tooling
- 🎮 Unity / mobile game development
- 🐍 Python CLI, TUI, and Linux automation
- 💎 Ruby / SketchUp extension development
- 🧱 TypeScript SaaS platforms and modular monoliths
- 🐧 Linux server tooling
- 🤖 Telegram / trading / admin bots
- 📊 Git/GitHub automation, release packaging, and project dashboards
- 🛠️ Documentation-first project structure
- 🧰 Operator tooling for server setup, repair, monitoring and configuration workflows
- 🔍 Quality workflow with tests, logs, audits, manual validation and controlled refactoring
- 🧪 Internal developer/infrastructure tools for project inspection, workflow automation and safer operational checks
Automation and AI-assisted workflows are part of my toolkit for research, audits, documentation and faster iteration. My main focus remains on system design, verification, integration, stabilization and bringing tools to a working state.
| Area | What I do |
|---|---|
| Linux / server tooling | CLI/TUI tools, systemd, configuration workflows, repair flows, health checks, telemetry/status parsing |
| Developer tools | local utilities, Git/GitHub automation, release packaging, dashboards, repeatable workflows |
| SaaS / platform foundations | TypeScript platforms, modular monoliths, clean module boundaries, backend/frontend foundations |
| 3D workflow | SketchUp/Ruby tooling, OBJ import workflows, pipeline helpers, geometry cleanup |
| Browser utilities | Chrome extensions, local-first browser tools, usage tracking, productivity helpers |
| Game prototypes | Unity/C# prototypes, gameplay experiments, mobile/game concepts |
| Automation / bots | Telegram/admin bots, trading bot prototypes, operational helpers |
| Documentation-first workflow | README files, changelogs, handoffs, architecture notes, audit checklists, release notes |
| Project | What it is |
|---|---|
| armactl · Website | Python/Linux TUI and server management tool for installing, repairing, managing and monitoring Arma Reforger Dedicated Server |
| Deus AI Limits Extension | Local-first Chrome extension for monitoring Codex and Claude usage limits from signed-in browser sessions |
| Deus Commit Chart | Local Git commit activity chart generator that outputs a self-contained HTML report |
| DeusApps OBJ Importer Lite | Geometry-only OBJ importer for SketchUp workflows, focused on clean OBJ import, orientation fixes and scene cleanup |
| MIA Platform | Private TypeScript SaaS foundation for municipal administrative workflows and modular platform experiments |
| bear_data_export_bundle | Python CLI exporter for Binance Spot OHLCV market data to CSV |
| Miner_Unity | Unity miner game prototype and gameplay concept |
| Tower-Cube | Unity/C# game prototype |
| Space-SHUMP-Plus | Arcade-style Unity prototype |
| HabitsBuilder | Contributor project: C# habit tracker with reminders and Google Calendar integration |
| TradingBinanceBot | Public documentation hub for a trading bot system |
| DeusBinanceBot | Trading/automation bot prototype |
| BinanceConvertRangeBot | Binance-related automation prototype |
| NotesApp | Android notes utility |
| CalculatorApp | Android calculator utility |
- Maintaining and improving armactl as a practical server management tool
- Developing DeusApps as a public hub for projects, utilities and downloads
- Improving Python/Linux automation and operator tooling
- Building local-first browser and workflow tools
- Designing TypeScript SaaS/platform foundations
- Building practical 3D workflow helpers for SketchUp/OBJ processes
- Creating reusable Git/GitHub automation and release workflows
- Maintaining internal developer/infrastructure tools for project inspection, workflow automation, validation and safer operational workflows
- Keeping documentation, reproducible setup and project structure clear
- Using tests, logs, audits and manual validation for controlled development
I usually start not with code, but with understanding the system: what is being built, who it is for, what the boundaries are, and where the risks and future pressure points may appear.
Typical process:
- Define the problem and expected user/operator workflow.
- Describe the system core, module boundaries and baseline architecture.
- Capture risks, edge cases and possible future requirements.
- Build the first working foundation.
- Develop the project in small slices.
- Validate changes through tests, logs, manual checks and audit/review passes.
- Update the architecture when new requirements do not fit cleanly.
- Keep public documentation clean and internal technical notes separate.
This approach helps avoid chaotic feature growth, hidden coupling and fragile one-off fixes.
- GitHub: @dturovskiy
- LinkedIn: in/denysturovskiy
- Website: dturovskiy.github.io/deusapps.store
- armactl: dturovskiy.github.io/armactl-website

