Best used with an AI agent

40+ live apps, open data APIs, MCP servers, and 200+ guides - more than anyone wants to click through. Point your AI here and it reads the whole map and does the work: finds the tool, pulls the data, runs the analysis, and hands you the links.

Here for the open-source code? Your agent finds the right repo for you - and can even clone and deploy it.

Prefer to explore on your own? Go right ahead.

Paste this to Claude Code, Codex, or any AI agent:
Go to tigzig.com and read tigzig.com/llms.txt. It is a practitioner toolkit - 40+ analytics apps, open no-auth data APIs, MCP servers, open-source repos (github.com/amararun), and 200+ build guides. Help me [your task]. Surface the exact links; where there is an API or MCP, call it directly; and if I want to self-host, find the repo and help me deploy it.
How I work with outside projects

Sessions and execution. Same work, seen two ways.

This page is how I work, so you know before you reach out.

100% remote Calls 1-6 PM IST Sessions from $180/hr Execution from $60/hr

The work

Two kinds, same projects. Analytics, full-stack apps, the infra they run on. Built for small and medium businesses, not enterprises.

Sessions

Hands-on, over screen share. I work through your actual problem with you and get you up to speed on the tool .. Claude Code in VS Code, the Claude app, Claude in Excel and PowerPoint. What I cover is your call: frontend, backend, databases, models, pulling data from different sources, a full analysis end to end.

Two kinds of folks come for sessions. Experienced practitioners (typically 10-15 years in) who want to use the tool on their own work. And division heads .. CEOs, CFOs, heads of marketing, analytics, logistics, 20 to 30+ years in .. who want the architecture and the flow at a higher level, plus how to do their own role better with it.

Either way the sessions still center on you actually using the tool .. that is what makes the time pay off. You want to use it for your own work, and understand how your team works with it.

Execution

I build it. Database AI, report generators, machine learning models, automations, dashboards, full-stack apps with auth and access control. The heavy lifting and the tedious pieces that take time to get right. Same projects as the sessions .. I just do the work.

Where I go deep

Many examples of all of this are live on the main site .. apps, code, posts. Most are open source. Browse /browse-apps, /analysis, /guides.

Analytics and machine learning models

Large part of what I do .. analysis, dashboards, ad-hoc reports, machine learning models. Data science and decision sciences. As standalone offline projects or as full-stack interactive tools connected to live systems.

Live examples

TREMOR (multi-source macro signals across 8 categories), MFPRO (mutual fund analytics with composition drift), IMDB Dashboard (12M+ titles, 230M-row backend), VIGIL (Indian markets + corporate signals across 7 NSE tables). All listed at /browse-apps.

AI tools and agentic apps

A specialty. Helping figure out where AI fits and in what form .. sometimes a single AI app is enough, sometimes API chaining, sometimes a full agentic setup. Then everything that sits on top of the build .. orchestration, observability, validation, hallucination controls, and the cost-management layer (per-user budgets, model routing) that matters as much as the work itself .. smart models are excellent but expensive. Live AI apps in use by medium-sized teams, mostly for operations.

See it run

The Database AI suite at /database-landing .. multi-step reasoning agents that connect to multi-GB databases, write SQL, run analysis, generate PDF reports. MCP server directory at /mcp-landing is callable from any AI client (Claude, Cursor, custom).

Full-stack apps

Mostly React + Vite frontends, FastAPI backends, Postgres or DuckDB. Platform-agnostic though .. PHP / Apache / MySQL and other stacks too. Pick up whatever the team already runs on.

Live examples

TREMOR, MFPRO, IMDB Dashboard and VIGIL are full-stack apps shipped without login on purpose .. they're free public tools, no friction. DuckIt is the auth example .. guest sessions get 2-day file storage, logged-in users 7 days, owner level keeps files permanently. All on /browse-apps.

Self-hosted infrastructure

Hetzner and OCI VPS, Coolify for deploys, Docker, multi-tenant Neon Postgres.

What's running on it

Every app on /browse-apps and every API on /apis runs on this infra. tremor.tigzig.com, vigil.tigzig.com, mfpro.tigzig.com, briq.tigzig.com .. each its own subdomain, container and deploy.

Production security

Hardening applied across the whole stack .. cloud, frontend, backend, plus continuous monitoring of every request. A 99-item baseline checklist is published at /security as a useful starting point .. it's a sample of what I actually run.

The evidence

All my data APIs run open, no auth, public internet (see /apis) .. they take real-world attack traffic, and the hardening at /security is what came out of that. My ops command center sits in the open too .. logs.tigzig.com, multi-layer defenses. The app itself has delete access to ~200 GB of data and admin to 40+ apps and services. Six months without incident.

Cloudflare edge

Cloudflare Workers in production. Honeypot routes catch scanners; offenders go into a jail and get blocked at the Cloudflare WAF. Plus rate limits, agent-traffic logging, markdown content negotiation and subdomain SEO.

Where you see it

Every page on tigzig.com is fronted by these Workers .. every frontend and backend. The agent-traffic logger feeds an ops dashboard.

AI-agent discoverability (AEO)

tigzig.com is built agent-first. RFC 9727 catalog at /apis, /llms.txt with an intent map, MCP server directory at /mcp-landing, markdown twins of every page. Point an AI agent at the site and it maps the whole platform in one fetch.

The check

Ask any AI agent .. ChatGPT, Claude, Perplexity .. "what is tigzig.com". It will map the site from /llms.txt within seconds .. apps, APIs, MCP servers, recent posts. Including content published this week.

Basic SEO

Basic mechanics to keep pages findable .. sitemap structure, JSON-LD breadcrumbs, structured data, Bing Webmaster + GSC + IndexNow integrations. The plumbing underneath the AEO work above .. not deep SEO consulting.

The check

Tigzig pages show up in Google, Bing and ChatGPT's live web search. Nothing fancy, just the basics keeping pages findable.

Open-source analytical tools

Free tools I've built and shared. TREMOR for global macro signals, VIGIL for Indian markets and company-level info, MFPRO for mutual fund analytics, plus a set of portfolio and technical analysis tools, database converters and text-to-SQL apps. The data behind them is on /apis as zero-auth APIs and MCP servers.

How execution works

1

Billed on brain time, not the clock

I charge for the time I am actually on your project .. planning, reviewing, validating, verifying output. Claude Code does the heavy lifting on its own. I might be at my desk 10 hours running three projects, you get charged for the hours on yours, not the wall clock.

Calls during an execution project .. planning, reviews, screen-share walkthroughs .. are billed on call time too, separate from the brain-time hours on the build. Sessions are call time by definition, so this only applies to execution work.

2

Every sprint is pre-approved

Before a sprint I tell you roughly what I am planning. You approve an upper limit, say 3 to 5 hours or 5 to 10. I stop at that limit and report back. No runaway bills, no surprises. The plan is the intent .. what I aim to do within the cap. You see both up front.

3

The repo is yours. You can take over any time

Repo and documentation sit with you, or you have full control. Stop the project, pick it up later, hand it back .. no issue either way. Most of my clients work with Claude Code too, so the handoff stays clean. Same docs, same tool.

4

It goes live early, and I stay on it

These are not month-long builds handed over at the end. Your real users, usually a CXO's team, are on the app from 30 to 40% in, the moment basic flows work. So by the time we reach 90%, most of their issues are already fixed and it is in real use .. days to weeks, not months. By the final stretch, most clients prefer to handle the small UI tweaks themselves .. faster and cheaper at that point, and they know the app well by then. Flexible either way, they can do it or I can. I keep supporting through full rollout and beyond, stepping in whenever you want.

Rates

SessionsAI-coder training, setup help, build guidance
$180 / hr
ExecutionBuild work, charged on brain time
$60 / hr
Rates vary by region and engagement. The above are indicative.

All sessions and execution are prepaid .. PayPal, Razorpay, UPI, or bank transfer, whichever works for you.

Availability

Mode
100% remote.
Calls
1 to 6 PM IST. Wednesday to Saturday, typically.
Email
Always open, but I respond during the call windows above.
Queue
Schedule runs full most weeks. I take on what I can fit.
Timelines
I work to my own schedule, and in practice it's fast. The trade-off is that fixed deadlines or rush jobs don't fit .. same setup for everyone, including long-running clients.

Get in touch

Reach me on LinkedIn or at [email protected]. Tell me what you are trying to build and a rough sense of scope.

This is a different way of working than the old project-quote model. It only works if you are comfortable with hourly, sprint-capped, repo-in-your-hands, and live before it's finished. Suits some setups, not others - happy to talk through whether it fits yours.