DEV Community

Ananya
Ananya

Posted on

How I Deployed My AI/ML Portfolio in Under 5 Minutes Using Kuberns AI

A developer's honest experience with one-click AI deployment


A bit about me

I'm Ananya — an Applied AI Engineer focused on Computer Vision, ML Pipelines, and Intelligent Automation. I spend most of my time building end-to-end AI systems: training CNN models, building CV pipelines with OpenCV and TensorFlow, and packaging everything with Docker.

What I'm not great at? Deployment infrastructure. DNS configs, server setup, build pipelines — it's a whole other job. So for a long time, my projects lived on GitHub and nowhere else.

That changed when I entered the Kuberns AI Portfolio Hackathon 2026.


The Problem: Great Projects, No Live URL

I had built real AI systems:

  • EcoStream AI — environmental intelligence system analyzing real-time AQI data
  • Automated OMR Evaluation — computer vision pipeline for automated exam scoring
  • Face Mask Detection — real-time CNN-based safety monitoring system
  • Foodoscope — deep learning food image classifier
  • Financial Chatbot — NLP-powered finance assistant

All of them sat on GitHub. None had a live URL. And in 2026, if your project isn't live for most recruiters, it doesn't exist.


Entering the Hackathon

The Kuberns AI Portfolio Hackathon 2026 had one clear goal: deploy a live portfolio. Not build something from scratch. Not write a thesis. Just ship it, make it public, show proof.

The prizes were real:

  • Top 5 share a $10,000 prize pool
  • Top 30 get featured permanently on Kuberns' social channels
  • Top 100 get Amazon Pay gift cards
  • Internship/Full-time opportunity up to 10 LPA

But honestly, the bigger reward was finally having a live portfolio URL I could put on my resume.


Building the Portfolio

I built a single-page HTML portfolio with:

  • Dark theme with animated particle network (canvas-based, mouse-reactive)
  • Custom cursor with magnetic buttons
  • Scroll-reveal animations on every section
  • Architecture diagrams for each project showing the system pipeline
  • Skills grid organized by category
  • Contact section with GitHub, LinkedIn, and email links

The design philosophy: make it look like a product page, not a student assignment.

Every project card follows the same formula:

Project Name
Short problem → solution description
Tech stack tags
Architecture pipeline: Input → Processing → Model → Output
GitHub link + Demo link
Enter fullscreen mode Exit fullscreen mode

That architecture pipeline was the single biggest upgrade. It signals systems thinking instantly to any engineer reading the portfolio.


Deploying on Kuberns

Here's where it got interesting.

I expected deployment to be the hard part. It wasn't.

Steps I took:

  1. Went to kuberns.com
  2. Signed up (free)
  3. Uploaded my index.html file
  4. Clicked deploy

That's it.

No Dockerfile to write. No environment variables to configure. No server to provision. Kuberns AI handled the build, deployment, and hosting automatically.

My portfolio went live in under 5 minutes.

Live portfolio: https://ananya2306-portfolio-main-9ded0fe.kuberns.cloud/

Kuberns Dashboard Screenshot


What Makes Kuberns Different

As someone who has manually deployed on Vercel, Render, and set up Docker containers, the difference with Kuberns is the AI layer.

It doesn't just host files. It understands what you're deploying and configures the environment accordingly. For a static portfolio, that meant instant deployment. For more complex apps, it handles the build pipeline intelligently.

The one-click promise is real. I was skeptical. I'm not anymore.


Lessons from Building a Strong Portfolio

After multiple rounds of feedback and iteration, here's what actually matters:

1. Engineer your descriptions, don't just describe

❌ "Built a mask detection model"
✅ "Designed a computer vision pipeline for real-time mask compliance detection using CNN-based classification"

Same project. Completely different perception.

2. Architecture diagrams are gold

Video Feed → Face Detection → CNN Classifier → Alert System

Four words and three arrows. Engineers instantly understand the system. Add this under every project.

3. Deployment proof > everything

A GitHub link says "I wrote code."
A live URL says "I ship products."

That difference matters enormously to recruiters.

4. Organize skills by category

Don't dump 20 technologies in a list. Group them:

  • Programming
  • ML & AI
  • CV Libraries
  • Deployment
  • Engineering Tools

Recruiters scan in 8 seconds. Make it easy.


Final Thoughts

If you're a developer with projects sitting on GitHub and no live portfolio — just deploy it. The Kuberns hackathon is the perfect forcing function.

The hardest part isn't the code. It isn't even the design. It's just shipping.

Kuberns made the shipping part trivially easy. The rest was up to me.


Links:


Built and deployed as part of the Kuberns AI Portfolio Hackathon 2026

#kubernschallenge #kuberns #aichallenge #MachineLearning #ComputerVision #Deployment #Portfolio

Top comments (0)