Blue for Organizational Database
Your organization.
On the record.
People, departments, roles, sites, skills, certifications, vendors — the internal source of truth your HRIS, CRM, and spreadsheet all pretend to be. Built on the same primitives as the rest of your business, so the org chart connects to the projects, the projects to the customers, the customers to the invoices.
01 · Data model
People → departments → sites. All connected.
People reference their managers and departments. Departments reference parent departments and offices. Offices reference sites and vendors. Update one record; every connected view updates with it.
- Project ID
- Status
- Due date
+ 7 more
- Amount
- Due date
- Status
+ 7 more
- Company name
- Industry
+ 7 more
- Deal value
- Stage
+ 7 more
- Full name
+ 7 more
Create one source of truth.
Create records for all your business data, so you finally have one place to keep everything.
- Centralized data for your entire team
- Always up-to-date across all devices
- Scales with your organization
What an org database looks like on Blue.
Four record shapes that show up in every organizational source of truth. Each is just a Blue workspace; the references between them make it an org.
People & roles
Employees, contractors, partners, board members — every person as a record with the attributes that matter (role, manager, location, employment type, skills).
Departments & reporting
Departments reference parent departments; people reference their managers. The org chart is just a view over the same records.
Skills & certifications
Skills, training records, and certifications attached to the people who hold them. Scheduled automations flag what's expiring before it does.
Sites, vendors, the rest
Offices, warehouses, fleet, suppliers, MSPs — every entity your org touches as a record, referenced by the people and departments that work with them.
02 · The record itself
The whole picture. Per record.
Every person, department, and site carries the fields, the history, and the documentation that explains it.
Every attribute, native.
Text, dates, currency, references, formulas, lookups, locations, files. The 23 field types cover whatever a person, department, or site record needs to carry.
Every change, recorded.
The audit trail logs who changed someone's manager, who reassigned a department, who renewed a certification — and when.
Senior Engineer JD
Policies in context.
Job descriptions, employee handbooks, site procedures — written once and linked to the records they describe.
03 · Views
Directory. Org chart. Map. Table.
HR sees the directory. Leadership sees the org chart. Facilities sees people on a map. Finance sees them on a table grouped by cost centre. Same records, role-appropriate view.
04 · Lifecycle automations
Renewals. Reviews. Anniversaries.
Cron-style schedules sweep the records due for action. Certifications expiring in 60 days. Annual reviews this quarter. Five-year work anniversaries this month. Reminders go out automatically; nobody runs the list by hand.
status = 'overdue'- Report · Q4 Launch
- Task · Ship v2
- Ticket · Billing bug
- Deal · Renewals Q1
- Task · Review design
05 · Permissions
Salary, performance, references — scoped tight.
Workspace-, record-, and field-level controls. Everyone sees the directory. HR and managers see employment data. Compensation stays scoped to the comp committee. Performance notes stay scoped to leadership.
One price. Pay once. Forever.
Pay once for your tier — no recurring per-seat fees. Size the tier to your team and move up only when you outgrow it.
Starter
For freelancers & small teams
One-time payment
- 5 users
- 5 workspaces
- 2,000 records per workspace
- 5,000 records per org
- 10GB storage
- 250 automations / month
- 3 webhooks
- 3 dashboards
- 1 custom role
- 20 req/s API rate limit
- Community support
Growth
For growing teams
One-time payment
- 30 users
- 25 workspaces
- 2,000 records per workspace
- 25,000 records per org
- 100GB storage
- 1,000 automations / month
- 10 webhooks
- 10 dashboards
- 3 custom roles
- 50 req/s API rate limit
- Email support
Scale
For large organizations
One-time payment
- 150 users
- 100 workspaces
- 2,000 records per workspace
- 100,000 records per org
- 500GB storage
- 5,000 automations / month
- 50 webhooks
- 25 dashboards
- 5 custom roles
- 200 req/s API rate limit
- Email support
One platform.
The whole org.
Stop running the org out of three different systems and a dusty SharePoint. Start with one workspace — people, or departments, or sites — and connect the rest from there.