Features in depth
The full picture of what NeonPod does — no buzzwords, just the parts you'll actually use.
Time Tracking
Log hours the way your team actually works — not the way a spreadsheet wishes you did.
NeonPod accepts manual entries with notes and categories, a built-in timer for focus blocks, and automatic capture from your IDE via Activity tracking. Every path respects the same reporting and scoring pipeline, so your data stays consistent.
- Manual entries with categories aligned to how you describe work
- Timer mode for session-based logging without guesswork
- Optional IDE integration for hands-free coding time
- No keystroke surveillance — we care about contribution, not surveillance
Activity
Your editor already knows when you're in flow. Activity tracking listens on your terms — heartbeats that distinguish active coding from idle tabs.
Works with VS Code and Cursor today. Folder mapping ties repositories to the right projects so hours land where they belong.
- Heartbeat batches reduce noise while staying honest about active time
- Editor and workspace awareness without screen recording
- Maps local folders to NeonPod projects for clean attribution
Contribution Scoring
Four metrics — hours, tasks completed, delivery rate, and consistency (via participation streaks) — roll into one transparent score per member.
Weights are yours to tune per project, and they must sum to 100. Evaluation periods and lookback windows keep scores explainable: anyone on the team can see the math.
- Hours, tasks, delivery rate, and streak-based consistency
- Per-project weight sliders with validation
- Rolling windows and minimum periods before someone is scored
Sweat Equity & Pool Distribution
Set an inventor cut and divide the team pool by contribution scores. NeonPod uses objective metrics to suggest how effort translates into splits — perfect for co-founders, incubators, or revenue-share pods.
The goal isn't to replace your lawyer or your cap table — it's to ground conversations in data everyone can inspect.
- Configurable inventor cut alongside per-project scoring
- Objective inputs reduce the "who carried" debate
- Built for teams where fairness is the default expectation
Kanban Task Board
Tasks move from "todo" to "done" with dates that feed delivery metrics. Drag-and-drop boards keep state visible without adding ceremony.
Delivery rate connects started work to finished work — so hustlers who close loops get credit beyond raw hours.
- Status workflow tied to scoring inputs
- Assignees and due dates for accountability without nagging
- Project-scoped boards inside each pod
Reporting
Break down effort by member, project, category, and timeline. Charts follow the Neon terminal aesthetic — readable in a dark room at 11pm, where a lot of this product gets built.
Export to CSV when you need to take numbers to a spreadsheet, investor deck, or retrospective doc.
- Member, project, category, and timeline slices
- Exports for audits and retros
- Designed for honest review, not manager theatre
Pod Management
Pods are your teams: owners, admins, and members with invitations, roles, and optional read-only viewers.
Each pod can run multiple projects with different visibility, scoring weights, and memberships — so one incubator doesn't force a single template on every squad.
- Role-based access at pod and project scope
- Invitations and membership controls
- Multi-project pods without shared-everything chaos
Security & Access
Data is scoped to your pod and projects. Super admins exist for platform operations — everyone else stays inside their memberships.
API routes enforce team and project gates; scoring configs and exports respect what each role is allowed to see.
- Team isolation on the data model
- JWT sessions with refreshed flags from the database
- Project-level permissions layered on pod roles
CLI & Terminal
Log time without leaving your terminal. The NeonPod CLI wraps the same API your editor uses into simple, scriptable commands.
Install globally with npm, run the setup wizard with your API key, and start logging. Flexible hour formats (2h, 2h30m, 2:30) mean you type what feels natural. An interactive project picker fills in the rest.
- One command to log: neonpod log 2h "Fixed auth bug" --project myapp
- Flexible hour parsing: 2.5, 2h, 2h30m, 2:30, 30m
- Interactive project picker when you skip the --project flag
- Works with CI/CD pipelines and automation scripts