Oracle3
Open-source trading engine and MCP server for prediction markets. Fee-aware no-arbitrage trading across related contracts, live on Kalshi, Polymarket and Solana or on paper.
ProfitRig shows an owner-operator what a mile really costs, what a load really paid, and what is left at the end of the week. Free rate-per-mile calculator, no account needed.
FinanceTypeScript · CSSGitHub @SebabrzekOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
Owner-Operator Cost Per Mile calculator — mobile-first PWA, Next.js + Supabase
Translation pending
Taken from the repository README
Loading the full README. The saved excerpt is shown below.
Owner-Operator Cost Per Mile calculator. Mobile-first PWA. Built for drivers who aren't tech savvy: big inputs, big numbers, plain English.
Stage 1 (this repo): Each driver creates an account and gets a saved cost profile. The app calculates true cost per mile (CPM), the minimum target rate, break-even monthly revenue, and projected monthly profit — live, as they type.
Stage 2 (next): Weekly load tracker that uses the saved CPM to flag profitable vs. losing loads.
1. Supabase — create the database tableRead the full README ↗Owner-Operator Cost Per Mile calculator. Mobile-first PWA. Built for drivers who aren't tech savvy: big inputs, big numbers, plain English.
Stage 1 (this repo): Each driver creates an account and gets a saved cost profile. The app calculates true cost per mile (CPM), the minimum target rate, break-even monthly revenue, and projected monthly profit — live, as they type.
Stage 2 (next): Weekly load tracker that uses the saved CPM to flag profitable vs. losing loads.
supabase-setup.sql in this repo, copy the whole contents into the editor, click Run.Sebabrzek/profitrig.NEXT_PUBLIC_SUPABASE_URL = https://qgwzxvqrpuodvuovxkcn.supabase.coNEXT_PUBLIC_SUPABASE_ANON_KEY = your publishable key (sb_publishable_...)*.vercel.app URL — that's your live app.profitrig.com) in Project → Settings → Domains.https://profitrig.vercel.app)npm install
npm run dev
Open http://localhost:3000. Sign up with any email/password (must be 6+ chars), then you'll land on the calculator.
.env.local already contains your Supabase URL + key.
src/app/page.tsx — main calculator screen (server component, auth-gated, loads saved profile)src/app/Calculator.tsx — interactive form + live resultssrc/app/login/ — sign in / sign upsrc/app/actions.ts — server actions (sign in, sign up, sign out, save profile)src/lib/supabase/ — Supabase clients (browser, server, middleware)src/middleware.ts — refreshes the user session on every request, redirects to /login if not signed insupabase-setup.sql — the database schema + row-level-security policies (run this once in Supabase)public/manifest.webmanifest + public/icons/ — PWA config, "Add to Home Screen" worksAdd loads table keyed by user_id with: date, broker, miles, rate paid, optional fuel cost, profit/loss vs. saved CPM, week aggregates. Same auth, same shadcn-style UI. Will reuse the saved cost_profiles row.