SYSTEMS · SOFTWARE · SECURITY

Tushar Nipane

Building dependable software systems for real-world problems.

B.Tech Computer Science student working across software engineering, security research, systems thinking, and practical AI.

View Selected Work

GitHub

Contact me ↗

PRAKRITI / MULTI-SOURCE INTELLIGENCE

01 / INPUT

MULTI-SOURCE SIGNALS

02 / FUSION

EVIDENCE + TRUST

03 / ANALYSIS

HAZARD-SPECIFIC RISK

04 / OUTPUT

PRIORITY + EXPLANATION

CONCEPTUAL FLOW · ACTIVE BUILD

CURRENT

Building Prakriti

SECURITY

Vulnerability research

LEADERSHIP

CEC · Technical Lead

COMMUNITY

NEC · Entrepreneurship

SELECTED WORK / 01

A small set of projects that show how I approach technical problems, architecture, implementation, and verification.

SYSTEM FLOW · PROTOTYPE

01 / SIGNALS

Multi-Source Signals

02 / TRUST

Normalize + Verify

03 / ANALYSIS

Fuse + Assess Risk

04 / OUTPUT

Priority + Explanation

Simplified view of the documented Prakriti system architecture.

SYSTEMS · DISASTER INTELLIGENCE

Prakriti

Multi-source disaster intelligence that turns fragmented environmental signals into prioritized, explainable warnings.

PROBLEM

Fragmented disaster-warning signals

CONTRIBUTION

Technical research · Architecture specification · Tech-stack synthesis

STATUS

Active build · Validation pending

View Prototype ↗

CASE STUDY IN PREPARATION

How I Engineer

01 / UNDERSTAND THE PROBLEM

Prakriti began with fragmented warning signals, not with a preferred model. The first question was how weather, satellite, river, historical, and local environmental evidence could be understood together.

02 / BUILD DELIBERATELY

Each source is normalized before fusion, while hazard-specific analysis stays separate so different disaster risks are not forced through one universal model.

03 / VERIFY THE RESULT

Nature-related observations remain supporting evidence, not standalone predictions. Confidence should reflect source agreement, reliability, and uncertainty, while every warning should explain why it was raised.

SECURITY RESEARCH / RESPONSIBLE DISCLOSURE

Studying how real systems fail—without turning the work into spectacle.

Identified and responsibly reported a high-priority access-control vulnerability affecting premium-resource access in a major SaaS platform.

Technical details remain limited pending disclosure permission.

AUTHORIZATION BOUNDARY

REQUEST

UNTRUSTED

IDENTITY

ASSERT

POLICY CHECK

EVALUATE

ALLOW / RESOURCE

DENY / BLOCK

Beyond the Build

TECHNICAL LEAD — CEC

Competitive Exam Cell

Technical responsibility shaped by coordination, planning, communication, and working with peers.

MEMBER — NEC

National Entrepreneurship Challenge

Cross-disciplinary collaboration and exposure to entrepreneurship, communication, and different technical perspectives.

TECHNICAL COMMUNITY

Hackathons, workshops, and independent learning

Regular participation across technical events and workshops.

Quackathon: Top 1,000 of approximately 3,000 teams.

BUILDING / Prakriti

LEARNING / Systems + Security

EXPLORING / Practical AI

CONTACT / OPEN TO CONVERSATION

Interested in systems, security, or difficult technical problems?

Start with the work, inspect the evidence, or send a direct note.

Email Tushar

GitHub