DEV Community

Tarun D Hullur
Tarun D Hullur

Posted on

Slide_Hustle

Hacktoberfest Open-Source AI Challenge Week 2: Side Hustle Submission đź’¸

This is a submission for the Hacktoberfest Open-Source AI Challenge Week 2: Side Hustle

What I Built

Meet Slipstream, a receipt management and expense-tracking tool built for freelancers, independent workers, and small business owners who want to spend less time on paperwork and more time on meaningful work.

Managing business expenses can quickly become messy. Receipts get lost, important totals are forgotten, and organizing expenses manually takes valuable time. Slipstream aims to make this process simpler with a clean, easy-to-use receipt inbox and AI-assisted receipt scanning.

Key Features

AI-powered receipt scanning: Upload receipt photos and use a local vision model to extract information.

Expense tracking: Keep track of business spending and view monthly expenses.

Receipt organization: Organize expenses by categories such as meals, travel, and office supplies.

Search and review: Find receipts and identify entries that need attention, such as missing dates or totals.

Manual expense entry: Add expenses yourself whenever you prefer.

Privacy-focused AI: Use a locally configured Ollama vision model instead of relying on a hosted AI API.

Local data storage: Receipt records are stored on your device, helping keep your business information under your control.

The goal is to make expense tracking less frustrating while giving users more control over their financial information.

Demo

https://slidehustle.netlify.app/

Code

https://github.com/tarundhullur/Side_Hustle.git

How I Built It

Slipstream combines an expense-management interface with an AI-assisted receipt-processing workflow.

  1. Receipt management

The application provides a central receipt inbox where users can view their records, search for expenses, filter by category, and identify entries that require review.

  1. AI-powered extraction

For receipt scanning, Slipstream uses an open vision model through Ollama. The application suggests the gemma3:4b model as an option.

The intended workflow is to submit a receipt image to the configured local model and use its analysis to help organize the expense information.

  1. Privacy by design

One of the main ideas behind Slipstream is that financial records can contain sensitive information.

Rather than depending on a hosted AI API, the receipt-scanning workflow can use a vision model running on a machine controlled by the user. The application also states that original receipt images are not saved after analysis.

  1. Manual entry and expense review

AI is not required for every task. Users can enter expenses manually, select categories, record totals and optional tax amounts, and add payment notes.

This provides a practical alternative when local AI scanning is unavailable or a receipt needs to be entered by hand.

  1. A simple, focused experience

The interface focuses on the tasks that matter most: adding receipts, reviewing expenses, tracking monthly spending, and keeping business records organized.

Technology to highlight: Ollama and the gemma3:4b vision model are identified by the application. Add your actual frontend framework, programming languages, database or storage approach, and other libraries here.

Why Does Open Innovation Matter?

Open innovation is at the core of Touch Grass because offline privacy, complete system transparency, and low-latency execution were non-negotiable for an interactive trail and outdoor companion.

Relying on closed proprietary APIs creates several bottlenecks:

  • Connectivity Restrictions: Closed models require constant, active internet access—making them completely unusable on remote outdoor trails or off-grid locations where network connectivity is spotty or nonexistent.
  • Data Privacy & Ownership: Users exploring local trails or personal routes shouldn't have their location telemetry, activity logs, or environmental data harvested or locked into proprietary cloud servers.
  • Cost & Vendor Lock-in: Proprietary APIs incur per-request token costs that limit iteration, scaling, and long-term maintenance. Open-source models allow complete flexibility to fine-tune locally, swap lightweight weights, and deploy on cost-effective infrastructure like Render without unpredictable billing spikes.

By using an open-source approach, Touch Grass runs efficiently, respects user data privacy, and delivers reliable offline utility without reliance on closed ecosystem constraints.


Top comments (0)