Database Operations
Every read and write against the PostgreSQL database behind your workspace. This includes loading record lists, opening a project, saving a form, running a filter query, generating a report, or executing an automation that touches database rows.
What drives this up:
Bulk record imports, large table queries, dashboards that aggregate many rows simultaneously, automation rules that loop through large datasets, reporting jobs that join multiple tables.
AI Assistant Queries
Every question submitted to the YBNW One AI assistant is a query against your workspace data using a read-only Supabase role. The AI reads your actual records — tasks, invoices, contracts, leave balances, pipeline values — and produces workspace-specific answers.
What drives this up:
Frequent natural-language queries by many team members, predictive forecast requests (revenue, cash flow, headcount), document intelligence extractions (receipt OCR, invoice field parsing, contract metadata).
Automation Rule Runs
Each time an automation rule fires — a trigger is matched, conditions are checked, and one or more actions execute — it counts as a run. Rules can run on record creation, field updates, time schedules, or manual triggers.
What drives this up:
Rules that trigger on every record save, high-frequency scheduled jobs (hourly or daily batch actions), rules that send notifications to many users, multi-step action chains that touch several tables.
Integration Sync Cycles
When YBNW One pulls data from or pushes data to a connected third-party system — an accounting package, HRIS, payment processor, calendar, or webhook endpoint — each complete round of synchronisation counts as a sync cycle.
What drives this up:
Frequent sync intervals (sub-hourly), multiple connected integrations running simultaneously, large batch payloads, bidirectional sync with high change rates on both sides.
File Storage
All files uploaded to the workspace — documents attached to projects, receipts attached to expense claims, contract PDFs, employee documents, asset images, and mail-merge templates — consume storage. Files are encrypted at rest in the Supabase storage layer.
What drives this up:
Bulk receipt uploads from expense management, contract libraries with versioned PDFs, project file archives, training materials in the L&D module, high-resolution asset images in inventory or facilities.
Report Generation
Scheduled and on-demand report jobs — financial statements, payroll summaries, project variance reports, audit export packages, executive dashboards — each consume a report generation credit when the system compiles and renders the output.
What drives this up:
Daily automated report packs emailed to leadership, end-of-month financial close reports, payroll summary PDFs, compliance audit export packages, large pivot dashboards refreshed on schedule.