Portfolio · India

Abeer Choubey

Building software and the systems behind it.

Backend Linux Infrastructure Automation

View work Say hello
India · IST

Press / to search · ? for keysTap Search to jump around

About

Who

About Abeer

I'm a student developer in India interested in backend engineering, Linux infrastructure, automation, and practical software products. I've worked on SaaS backends, lead-management tools, server-hosting experiments, and container-based provisioning workflows.

I enjoy debugging real deployment problems and understanding how applications, databases, networks, and infrastructure fit together.

How I work

  1. I describe a project by what I built and tested, and say plainly what I did not.
  2. When a deployment breaks, I want to know which layer failed: application, database, network or host.
  3. I try to turn experiments into documented, testable projects.

Focus areas

  • Backend and database-backed applications
  • Linux systems and self-hosting
  • Containers and deployment workflows
  • Automation and Discord integrations
  • Early-stage product development, marketing and outreach

Projects

Selected work

Four projects, each labelled with what it actually is. Open a case study to see what I built or specified, what it taught me, and what I am not claiming.

  • Built
  • Experiments
  • Planned
  • Proposed

Schematic. Boxes show how the parts relate, not a real screen or real figures.

Aurorax Cloud, schematic Schematic. A Linux node runs Incus/LXC containers and Docker services. A reverse proxy routes requests to services and Tailscale links nodes. Two planned parts, Discord-driven provisioning and a dashboard, are drawn dashed. DiscordProvisioning flowLinux nodeIncus/LXCcontainersDocker servicesReverse proxyTailscale networkDashboard health, expiryroutes toconnectsrequestcreatesrunsruns Aurorax Cloud, schematic Schematic. A Linux node runs Incus/LXC containers and Docker services. A reverse proxy routes requests to services and Tailscale links nodes. Two planned parts, Discord-driven provisioning and a dashboard, are drawn dashed. DiscordProvisioningflowLinux nodeIncus/LXCcontainersDockerservicesReverseproxyTailscalenetworkDashboard
  • Built
  • Experiments
  • Planned

Schematic. Boxes show how the parts relate, not a real screen or real figures.

01 Hosting and Infrastructure

Aurorax Cloud

An early-stage hosting project: Linux nodes, containers and the networking between them.

Parts built · platform not claimed

  • Incus/LXC (Exploring)
  • Docker (Exploring)
  • Tailscale (Exploring)
  • Reverse proxies (Exploring)
  • Discord bots (Exploring)

What it is

An early-stage hosting and infrastructure project involving Linux nodes, Discord workflows, container provisioning, and service operations. Experiments have included Incus/LXC, Docker, Tailscale, reverse proxies, and Minecraft hosting components.

Not claimed

  • A finished or production hosting platform.
  • Discord-driven provisioning or the dashboard. Both are planned.
  • Uptime, scale or usage figures of any kind.

Next

Next, I want to document which parts work and test them before building the planned parts.

What I built

  • Container provisioning experiments with Incus/LXC and Docker on Linux nodes.
  • Experiments with Tailscale and reverse proxies to connect and route between services.
  • Discord workflows around the service. Discord-driven provisioning is planned, not built.
  • Minecraft hosting components.

Planned, not built

  • Discord-driven provisioning of containers.
  • A dashboard for containers, node health and expiry dates.

What it taught me

  • Hosting involves more than starting containers: the networking between services and the running of the service are part of the project.
  • Saying which parts work and which are only planned keeps the project honest.

Stack

  • Incus/LXC (Exploring)
  • Docker (Exploring)
  • Tailscale (Exploring)
  • Reverse proxies (Exploring)
  • Discord bots (Exploring)

Topics

  • Linux nodes
  • Container provisioning
  • Service operations
Gymledger, schematic Schematic. On the left, what was built: the backend and its security measures. On the right, how gyms were reached: marketing and cold calling. Between them a dashed box stands for adoption, the gap the project taught me about. BackendSecurity measuresAdoptionMarketingCold calling protectsbuiltreachreach Gymledger, schematic Schematic. On the left, what was built: the backend and its security measures. On the right, how gyms were reached: marketing and cold calling. Between them a dashed box stands for adoption, the gap the project taught me about. BackendSecuritymeasuresAdoptionMarketingCold calling
  • Built
  • Experiments
  • Planned

Schematic. Boxes show how the parts relate, not a real screen or real figures.

02 Gym-focused SaaS

Gymledger

A SaaS for gyms, and a lesson in the gap between building software and getting it used.

Built · tested in part

What it is

A SaaS project for gyms involving backend development, security measures, marketing, and cold calling. The project provided practical experience with the difference between building software and getting users to adopt it.

Not claimed

  • Any number of users or gyms.
  • That the product is finished, polished or in wide use.
  • A particular tech stack.

Next

Next, I want to write up the product and its security measures properly before saying more about it.

What I built

  • The backend of the product.
  • Security measures around it.
  • Outside the code: marketing and cold calling to reach gyms.

What it taught me

  • Building software and getting users to adopt it are two different jobs, and the second does not follow from the first.
  • Marketing and cold calling are part of the work, not something that happens after the code is done.

Topics

  • Backend
  • Security
  • Marketing
  • Cold calling
Lead CRM, schematic Schematic. A Go terminal interface reads and writes a SQLite database, which can be exported to CSV. A dashed branch shows the web version on Supabase that the project moved toward. Go terminal UISQLiteCSV exportWeb versionSupabase reads, writesmoved towarddata movesexports Lead CRM, schematic Schematic. A Go terminal interface reads and writes a SQLite database, which can be exported to CSV. A dashed branch shows the web version on Supabase that the project moved toward. Goterminal UISQLiteCSV exportWebversionSupabase
  • Built
  • Experiments
  • Planned

Schematic. Boxes show how the parts relate, not a real screen or real figures.

03 Lead management tool

Go + SQLite Lead CRM

A lead tracker that started in the terminal, in Go, on SQLite.

Terminal version built

  • Go
  • SQLite
  • CSV
  • Supabase (Exploring)

What it is

A lead-management tool that began as a Go terminal UI backed by SQLite, with CSV export. The project later moved toward a web-based version using Supabase.

Not claimed

  • A finished web version.
  • That the tool is in use anywhere.
  • Any figures about leads or outcomes.

Next

Next, I want to document the schema and the export so the project can be tested, then decide whether the web version is worth finishing.

What I built

  • A terminal interface in Go for managing leads.
  • SQLite storage for the lead records.
  • CSV export of the data.
  • Moved toward a web-based version using Supabase (not claimed as finished).

What it taught me

  • A local SQLite file with a CSV export is a simple first shape for a lead tracker.
  • Moving toward a web version means thinking about hosting the data, not only storing it.

Stack

  • Go
  • SQLite
  • CSV
  • Supabase (Exploring)

Topics

  • Terminal UI
  • Lead management
  • Data export
Candidate workflow, proposed schematic Schematic of a proposal. Permitted sources feed a periodic refresh into a records store. Records feed a dashboard and the preparation of e-mail drafts. Drafts pass a human review gate before any outreach. Everything is drawn dashed because nothing here is claimed as built. Permitted sourcesPeriodic refreshCandidate recordsDashboardE-mail draftsHuman reviewOutreach only if approvedpermitted datafor approvalpreparesupdatesshows Candidate workflow, proposed schematic Schematic of a proposal. Permitted sources feed a periodic refresh into a records store. Records feed a dashboard and the preparation of e-mail drafts. Drafts pass a human review gate before any outreach. Everything is drawn dashed because nothing here is claimed as built. PermittedsourcesPeriodicrefreshCandidaterecordsDashboardE-maildraftsHumanreviewOutreach
  • Proposed

Schematic. Boxes show how the parts relate, not a real screen or real figures.

04 Proposed automation

Candidate Discovery and Outreach Workflow

A proposed workflow on paper: refresh records, draft e-mails, show a dashboard. A person reviews everything first.

Proposed · specification only

What it is

A proposed automation workflow for periodically refreshing candidate records, preparing personalized e-mail drafts, and presenting candidate information and statistics in a dashboard.

Not claimed

  • That it is built, running or tested.
  • That any candidate data has been collected.
  • That any message has been sent.

Next

Next, I want to settle what is specified and what is built, then split the specification into small pieces that can be built and tested one at a time.

What is specified

  • Periodic refresh of candidate records.
  • Personalized e-mail drafts, prepared for a person to review.
  • A dashboard showing candidate information and statistics.
  • Human review before any outreach.
  • Respect for source permissions and privacy.

Design principles

  • Respect source permissions and privacy.
  • Keep candidate records fresh by refreshing them periodically.
  • A person reviews every draft before any outreach.

Topics

  • Automation
  • Dashboard
  • E-mail drafts
  • Privacy

Stack

Technical focus

Tools I have used or explored in projects. A tool being listed says nothing about depth, so there are no bars or scores.

Markers

Used
Used in projects or day to day.
Exploring
Tried in experiments.
Learning
Still studying it.
Projects

Hover or focus a tool to see which projects it appears in. Click, tap or press Enter to pin the highlight; Esc clears it.Tap a tool to see which projects it appears in; tap it again to clear.

No tools are listed for this project.

Programming

Languages, with a note on level where it matters.

Databases and data

Small, practical data work.

Systems

Operating systems and containers.

Networking and web serving

Getting requests to the right place.

Other

Workflows and practice rather than products.

Away from the editor

Beyond coding

What I do away from the keyboard, and some of what I do at it.

  • Linux desktop customization

    Configuring my own desktop until it works the way I do.

  • Self-hosting

    Running services myself to see how they behave.

  • Server operations

    Keeping services up, and working out why they are not.

  • Arduino

    Tinkering with microcontrollers.

  • Keyboard modding

    Opening keyboards up to change how they feel and sound.

  • Karate

    Away from the screen entirely.

  • Fitness

    Exercise to balance the hours at a desk.

  • Cycling

    Riding a bicycle, with no screen and no terminal.

Ahead

Current direction

Turning experiments into projects that are documented and testable.

Strengthening backend and systems skills by turning experiments into well-documented, testable projects while pursuing academic goals and exploring future study paths in computing and software engineering.

Contact

Say hello.

Write to the general e-mail first. Use the other one only for sensitive matters.

General e-mail
choubeyabeer@gmail.com

General messages, questions and introductions.

Sensitive matters
sentinel.loqs@proton.me

Only for sensitive matters. Everything else goes to the general e-mail.

Discord

bsp.wm

Quick messages. Copy the handle and add me on Discord.

India, IST

Search and commands

Keyboard shortcuts

/ orCtrlK
Open search and commands
Esc
Close search, shortcuts or a project
Enter
Open the project you have tabbed to
←→ orjk
Switch between projects while one is open
?
Show this list
1–6
Jump to a section
c
Copy the general e-mail while Contact is in view
Single-key shortcuts

Single-key shortcuts only work when you are not typing in a field. Turn them off here if they clash with your screen reader or speech input.