CONTACT
Questions, corrections and responsible security reports can be sent to Ayronjins4@gmail.com.
About / Direction
The person behind the systems.
About technical content
The interests, principles and technical direction behind the work.
ABOUT / 06
About
The person behind the systems.
AYRON JINS / INDEPENDENT TECHNICAL WORK
Learn technology by building the stack.
I'm a technology enthusiast, and I'd rather build a system than just use one. Lately that's meant running a self-hosted home lab, poking at networking infrastructure, deploying local AI models, and putting together AI agents that can actually use tools.
What I keep coming back to is what's happening underneath the application: the servers, the network, the decision logic that quietly makes the thing work or not.
Reference / Quick facts
Ayron Jins at a glance.
Short factual answers to the questions people and search systems ask most often. Each one links to the page that documents it.
- Who is Ayron Jins?
- Ayron Jins is a student systems builder who works across AI agents, computer networking, Linux infrastructure, virtualization and self-hosted services. He designs, operates and documents the systems himself.
- What is his website?
- ayron.in is his official personal website and the primary source for his projects and technical writing.
- What does he build?
- An agentic computer-operation project called KHS AI, a self-managed homelab and network, a read-only infrastructure dashboard, a weekly technology news site, and a set of browser and server engineering tools.
- What is KHS AI?
- KHS AI is Ayron Jins's experimental agentic computer-operation project. It examines whether a language model can reason about a goal, use explicitly provided tools, observe the resulting state and verify outcomes while staying inside visible permission boundaries. Read the KHS AI case study.
- Who created KHS AI?
- Ayron Jins created KHS AI. It is a current exhibition project, documented at architecture and design level rather than as a deployed product.
- What is his homelab?
- A self-managed environment running Proxmox VE virtualization, Ubuntu Server hosts, Docker containers, an Nginx reverse proxy, DNS with AdGuard Home, TLS termination and firewall policy. See the homelab and networking case study.
- What does he know about networking?
- DNS resolution, IP addressing and subnetting, NAT and port forwarding, reverse proxies, HTTPS and TLS, firewall policy, and tracing a request end to end. Documented on the networking page.
- What does he know about AI?
- AI agents and controlled tool use, local model deployment with Ollama and Open WebUI, retrieval-augmented generation, and the engineering boundary between a model suggesting an action and a system performing one. Documented on the AI and development page.
- Are his tools publicly usable?
- Yes. The Tools Lab hosts a domain, DNS and TLS inspector, a browser-local subnet and VLSM planner, and a website metadata inspector. They run against a bounded backend and retain no scan history.
- Where is his code published?
- On GitHub at github.com/ayronjins. Public repositories include the SSRF-hardened API behind the Tools Lab, a read-only homelab observability dashboard, a scope-enforcing security assessment tool, a crawler-verification utility, and the source of this website.
- How can he be contacted?
- By email at Ayronjins4@gmail.com. Professional profile: LinkedIn. Source code: GitHub.
What interests me
The layers are connected.
SYSTEMSHow operating systems, services and infrastructure work together.
NETWORKSHow information moves between machines.
AIModels interacting with tools and external environments.
AUTOMATIONTurning repeated digital processes into workflows.
HARDWAREUnderstanding the machines underneath software.
SOFTWAREInterfaces and systems that connect the layers.
Skills / connected capabilities
No percentages. Just relationships.
INFRASTRUCTURE
NETWORKING
AI
DEVELOPMENT
SERVICES
Skill graph / conceptual
Tech stack explorer
DOCKER / CONTAINERIZATION
USED FOR / Containerized services.
CONNECTED TO / Portainer, Linux and self-hosted applications.
RELATED KNOWLEDGE / Ports, volumes, networks and environment variables.
Principles I value
Technical judgment matters.
UNDERSTANDING OVER MAGICKnow what tools are actually doing.
OWNERSHIP OVER DEPENDENCELearn how to run systems yourself where practical.
DEBUGGING OVER GUESSINGTrace a failure to the responsible layer.
BUILDING OVER ONLY CONSUMINGUse technology as something to experiment with.
SIMPLICITY OVER COMPLEXITYKeep systems understandable.
SAFETY OVER POWEREspecially when building agents and automation.
Currently exploring
Curiosity without pretending it is complete.
AI AGENT ORCHESTRATIONUnderstanding coordination between models, tools and state.
ADVANCED NETWORKINGGoing deeper into infrastructure paths and diagnostics.
OBSERVABILITYMaking system behavior easier to inspect.
MODEL EVALUATIONTesting whether AI workflows are useful and reliable.
AUTOMATION WORKFLOWSTurning repeated tasks into controlled processes.
SECURITY FUNDAMENTALSLearning defensive practices and safer boundaries.
Identity / Ownership / Accuracy
Who actually runs this site.
SITE OWNER
Ayron Jins
This is my personal engineering portfolio. I write and maintain the content, run the site itself, and use it as a running record of what I'm building and learning.
CONTENT POLICY
Everything claimed as a project here is something I've actually built or tested. Where a diagram or section is conceptual rather than a finished system, it's labeled that way.
PRIVACY
There's no account system here and no advertising trackers. Basic page and performance data comes from first-party Umami measurement, with no profiling cookies involved. See the privacy notice for the full picture.
SECURITY
The website uses HTTPS and publishes a standard security.txt contact for responsible disclosure.
Contact
Reach out about systems worth building.
LET’S CONNECT
Build. Operate.
Understand.
If you're working on something in infrastructure, networking, or AI systems and think it's worth a conversation, reach out.
Ayronjins4@gmail.com ↗AYRON JINS / FINAL TRACE
I build systems to understand how they work.
From servers and networks to AI agents and software.