For enterprises · groups, entities and sites
Every site.One system of record.
Contracts, procurement, people and projects across every entity and site — on shared engines, with sign-in through your identity provider and access that follows your organisation, down to the site.
Six kinds of thing · one group
- Contract
- Purchase order
- Vendor
- Person
- Project
- Policy
01 — Sound familiar?
The system of record is a spreadsheet.
Every department bought what it needed — and the truth now lives between them: exported, re-keyed, attached to an email, reconciled at month end by someone who knows where everything is.
02 — Built in
Built in, not bolted on.
Files, docs, approvals, site forms, reports and a calendar — reading the same records at every site, so nothing is reconciled between systems.
Documents with the record's access.
Drawings, certificates and contracts carry the access of the site and the record they belong to — no parallel file-share permissions to keep in step.
03 — Everything is a record
Everything the group runs is a record.
Contracts, purchase orders, vendors, people, projects and policies — six kinds of thing, one way of working, in every entity and at every site.
Steel supply framework
Halden Infra · Halden Materials
- Owner
- Rahul Iyer
- Value
- $4.2M
- Term
- 3 years
- Renews
- in 14 months
Every record comes with
- History
- Access
- Files
- Rules
- Ask
Active
04 — Access, start to finish
One profile, every site.
01 / 05
Sign-in through your identity provider.
Connect Microsoft Entra ID over SAML. The metadata and the callback are validated before anyone depends on it; then SSO is required and MFA enforced.
02 / 05
One profile for a role.
A Site manager profile says what the role gets in each module — projects, orders, people, files. It's versioned: v4 is drafted, then published.
03 / 05
Your groups, mapped.
The directory group for North's site managers is mapped to the profile over SCIM. Membership comes from your directory, not from a list someone keeps.
04 / 05
Rolled out in waves.
The pilot site first, then the region. Each wave shows who's effective, who's blocked and what needs a look — and it can pause.
05 / 05
Off in one place, off everywhere.
When someone leaves, they're removed in the directory. SCIM takes their access away across the modules, and the audit shows when and why.
05 — Ask
Ask across the whole group.
FyBrain answers from the records — budgets, policies, suppliers — and shows where each answer came from.
AskFyBrainAnswer
“Which projects are over budget this quarter?”
Two: North ring road package 2 (4% over, on rebar prices) and the West-1 depot (2% over). Both carry a variance note.
- PRJ-0712
VendorMaterialsVEN-0412
Ferrum Steel Ltd
Structural steel · 9 sites
ProjectProject SystemPRJ-0712
North ring road · package 2
Halden Infra · 3 sites
PolicyAutomationPOL-0031
Purchases over $50K
Every site · every entity
06 — A quarter
The first quarter, in waves.
A group-wide move is a sequence, not a switch-over weekend: sign-in, profiles, a pilot site, then the rest.
Week 1
Sign-in, your way
Your identity provider connected; SSO required and MFA enforced from the first login.
Week 3
Profiles for roles
Access profiles for site managers, engineers and finance — versioned, and mapped to your groups.
Week 6
A pilot site
One site moves in first. Masters and open orders imported; both systems run side by side.
Week 9
Waves, not a big bang
The rest of the sites follow in waves; each rollout shows who's live and who needs attention.
Week 13
One source of truth
Group reporting comes from the records. The old exports are archived, not maintained.
07 — Access
Every site sees only what's theirs.
The same orders, contracts and people — scoped to the entity and site each person works in. Group finance sees the group; a site manager sees the site.
08 — Moving in
Bring the masters with you.
Vendor masters, open orders, employee lists and contract archives — exported from the old systems, imported as records and matched to typed fields. Anything that needs a look is flagged, not guessed.
09 — Trust
Plain facts, no borrowed badges.
Where the group's records live, how people sign in and who can reach what — stated plainly. Where something isn't in place yet, we say so.
Sign-in you control
SSO through your identity provider (OIDC, SAML, Microsoft Entra ID or Google Workspace), MFA enforceable, sign-in limited to your email domains.
Leavers lose access everywhere
Remove someone in your directory and SCIM takes their access away across the modules — recorded on the audit.
Where it lives
Hosted in India (AWS Mumbai) for launch. Other regions may follow, by plan or agreement.
Locked in transit and at rest
TLS on the way in and out; storage encrypted at rest where it's configured.
Who can see what
Role-based access on every record — the permissions engine checks each request.
What changed, and who
Changes are logged with the person, the time and what was there before.
AI, only when you use it
AI features call outside model providers only when you use them — and every answer shows its sources.
Yours to take
Export and deletion on request during launch; after cancelling, exports stay available for 30 days where technically possible.
10 — The same records
The same records at every size.
A site, an entity, a group — Fyboard is the same system at each step, which is why a pilot site can become the whole group without a second migration.
- See the pageFor youOne person
- Clients & contracts
- Invoices & receipts
- Files & notes
- See the pageFor teamsA team or department
- People & roles
- Approvals
- Shared views
- See the pageFor startupsA growing company
- Hiring & payroll
- Finance & vendors
- A data room
- You're hereFor enterprisesA group of companies
- Access profiles
- Staged rollout
- Audit at scale
11 — Pricing
Pricing, plainly.
Each module the group would use, where it stands today and where its prices live. Group-wide terms, regions and service levels are agreed in the contract — not implied on a web page.
The modules you'd use
- AlphaCoreContracts across entitiesPublicPricing
- PeoplePeople, sites and payrollInternal betaPricing
- MaterialsVendors, orders and materialsIn pipelinePricing at launch
- FinanceLedgers, payables, receivablesIn pipelinePricing at launch
- Project SystemProjects, budgets and deliveryIn pipelinePricing at launch
- AutomationApprovals and policiesInternal betaPricing
Available today
FyTools
Standalone tools you can use now — for invoices, PDFs, images, screenshots and payroll.
- Free ForeverFree forever
- Cloud ProFrom $4 per tool / month
- TeamFrom $19 per seat / month
12 — Questions
Fair questions, straight answers.
What IT, security and operations ask before a group-wide move.
Do you support SSO and SCIM?
Yes. Sign-in through OIDC, SAML, Microsoft Entra ID or Google Workspace; SCIM provisioning maps your directory groups to access profiles. SSO can be required and MFA enforced for the whole organisation.
Can we roll it out gradually?
Yes. Access profiles are versioned and rolled out in waves; each rollout shows who's effective, who's blocked and what needs attention, and it can pause.
Are you SOC 2 or ISO 27001 certified?
Not today. Fyboard is in internal beta, and its security controls are being documented as it moves to public launch. We'll say so plainly on this page when that changes — and not before.
Where is data hosted? Can we choose a region?
For launch, data is hosted in India (AWS Mumbai). Other regions may be offered by plan or agreement.
Do you offer service levels?
Only where they're expressly agreed in a contract. Nothing on this site should be read as a promised uptime.
How do we move from our current systems?
In stages. Masters and open records come in from exports (CSV or Excel), matched to typed fields, with rows that need a look flagged. A pilot site can run side by side with the old system while you move.
Does it handle several entities and sites?
Yes — records carry their entity and site, and access can be scoped to them, so a site sees its own work and the group sees the whole.
Can we use it today?
Fyboard is in internal beta, and each module opens as it reaches public launch — you can see where each one stands on this page.
Does AI read our records?
Only when someone uses an AI feature. FyBrain answers from your records and shows where each answer came from; outside model providers process data only for the features you choose to use.
Can we leave with our data?
Yes. During launch, exports and deletion are handled on request; after cancelling, exports stay available for 30 days where technically possible.
Your group's system of record
Start with one site. Grow into the group.
A pilot site first — sign-in, profiles, its masters and open orders. The rest follow in waves, on the same records.
Sign-in & access
Your identity provider, profiles for roles, and SCIM keeping them in step.
- Profiles
- Policies
A pilot site
One site's vendors, open orders and people — running beside the old system.
- Orders
- People
Group reporting
Spend, progress and contracts across entities, straight from the records.
- Contracts
- Projects