The system of record for how work actually happens.
Fyboard is a records-first operating system for modern execution. We build engines, not apps. Three shared engines — FyBrain (intelligence), Workflow (orchestration), and FyDrive (files and documents) — sit underneath every module.
Fyboard is built by Fybyte, the digital arm of Raj Corporation Limited (RCL), a ₹4,500 crore EPC company in India. The platform was forged on a real construction site — not in a vacuum, not in a deck, not in a venture office. The schema graph behind it is 620+ models and still growing every week.
Enterprise software has gone wrong in two opposite directions. Fortresses (SAP, Oracle, Workday) dictate workflows; modern SaaS archipelagos (Notion, Linear, Slack) are delightful alone but isolated together. Most companies pick a side. We started building the bridge.
Internal beta at RCL covers AlphaCore (contracts), Automation, FyBrain (intelligence), and FyDrive (files). Public access is gated behind the waitlist. By 2029, Fyboard will replace SAP at RCL — that is the public bet.
For more on the founding argument, read /origin. For the principles, read /manifesto. To apply to build with us, see /careers.
Fyboard is the operating system we built to run a ₹4,500 crore EPC company.
Engines, not apps. Forged in concrete. Refined by code.
Every contract, file, form, document, person, approval, and automation run inside Fyboard is the same kind of thing — an operational record. Modules don't integrate. They compose, because they all speak the same vocabulary.
"Once everything is a record, modules don't need bespoke integrations to talk to each other."
Fyboard architecture · principle 01
Each module does one job, well, over the same operational records. Some are already inside RCL on internal beta. Others are still being built.
Contract lifecycle
Drafting → negotiation → eSign → renewal — every clause is a record.
Records & forms
Vendor intake, employee onboarding, audit checklists — typed, queryable, governed.
Collaborative documents
Memos, SOPs, RFCs — versioned, citation-aware, AI-assisted.
File & object storage
Drawings, scans, signed PDFs — lineage-safe, permissioned, versioned.
AI engine, in-tenant
OCR, extraction, summarisation — runs in your region, never ships data out.
Record-aware automation
Approvals, SLAs, escalations — one engine across every module.
Team directory
Roles, permissions, reporting lines — the spine other modules read from.
Every module composes from the same backend engines, and every screen is built from the same frontend engines. Improvements propagate to every surface, instantly.
Intelligence — OCR, extraction, summaries. Runs in-tenant.
Orchestration — approvals, routing, SLAs, audit.
Storage — files, versions, lineage, permissions.
Record-table engine
Calendar over records
Spreadsheet — cells are records
Computed values across records
Cross-module design primitives
Interactive API explorer
Embeddable database modeller
Structured-data inspector
Eleven engines power seven modules. The same comment is the same comment everywhere. The same approval is the same approval. There is no duct-tape between products because there is nothing to tape together.
Fyboard is built by Fybyte, the digital arm of Raj Corporation Limited — a ₹4,500 crore Indian EPC company. The team is deliberately small. Schema-first. No marketing-led roadmap.
We're inside the company we're building for, not adjacent to it. That changes what we ship and what we refuse to ship.
Most AI-first platforms quietly route your records through a global LLM API. We don't. Fyboard runs the intelligence layer inside the same region as your storage layer — and inside your tenant.
Our AI engine sits inside your cluster, in your region. No prompt or document is shipped to an external LLM provider.
Default tenancy is in India. Other regions are configurable. Where your data lives is a deployment decision, not a guess.
Files in FyDrive, records in DataBoard, contracts in AlphaCore — all stay inside the boundary your IT team draws.
Built this way because the same regulators we work with on highways and power grids audit our software. Compliance isn't bolted on — it's the floor we started from.
Solo operators don't have to graduate to a different tool when their team grows. The records, the workflows, the files — they all stay. Only the surface area changes.
FyDrive: secure links, granular permissions, lineage you can audit.
AlphaCore: send, sign, store. Every clause is a record.
FyBrain: drop in PDFs and FyBrain extracts the structure.
Automation: form → folder → notify → archive, without glue code.
The freelancer's signed PDF and the enterprise's procurement chain are the same kind of record.
Fyboard is in internal beta. Four modules ship for RCL teams and close testers right now. Three are in active development. Public access is gated behind the waitlist on purpose — we open modules when they're stable, not when the calendar says we should.
The engines hold real production data — contracts, audits, signatures. Schema stability and migration safety come first. We'd rather wait six months than ship something that locks our users into a shape we'd later regret.
PDF tools, OCR, file converters, a lightweight eSign. Free with fair usage caps, opening before the modules. They're the easiest way to feel the engines without committing to the platform.
See current toolsFour horizons. We move forward when the previous one is stable, not when the calendar says so.
AlphaCore, FyDrive, FyBrain, Automation are running inside RCL. DataBoard, FyDoc, People are hardening alongside.
Free utilities open first. Modules open one by one once schema stability is proven outside RCL.
Finance, Procurement, Projects, Analytics — each one a module on the same records spine.
Target horizon for replacing the current ERP stack at RCL with Fyboard.
Grouped into four conversations: what the platform is, how the trust model works, where it stands, and what we're committing to.
A records platform with seven modules on top. Every contract, file, form, document, person, approval and automation run is the same kind of thing — an operational record — which is how the modules compose without bespoke integrations.
Read the definitionA row is a database concept — fields in a table. A record is an operational concept — it carries ownership, history, context, automation hooks, intelligence, and permissions. Modules read and write the same records, so a contract in AlphaCore is the same kind of object as a memo in FyDoc or a file in FyDrive.
See the records spineSaaS suites are integrated with duct tape — each app has its own model and the seams show. ERPs force your operations into their model. Fyboard is records-first: every module reads and writes the same operational records, so composition is native, not bolted on.
In-region by default. FyBrain — the AI engine — runs inside your tenant, in the same region as your storage. No prompt or document is shipped to an external LLM provider. Default tenancy is in India; other regions are configurable.
Region & sovereigntyAudit logs by default. Two-tier permissions (role-based + feature-based). In-tenant AI, in-region storage, lineage-safe file access. Built this way because the same regulators we work with on highways and power grids audit our software.
Yes. Records are typed and queryable, files come with their lineage, and contracts ship with their full audit trail. Export is a first-class operation, not a customer-success ticket.
Because the engines hold real production data — contracts, audits, signatures. Schema stability and migration safety come before broader release. We open modules when they're stable, not when the calendar says we should.
Live for RCL teams and close testers: AlphaCore, FyDrive, FyBrain, Automation. Hardening: DataBoard, FyDoc, People. Public access for all of these is gated behind the waitlist.
See full statusPDF tools (merge, split, compress, convert), image + OCR utilities, file converters, web scraping tools, and lightweight eSign. Free with fair usage caps. They open before the modules — the easiest way to feel the engines without committing to the platform.
Try the toolsFyboard is built by Fybyte, the digital arm of Raj Corporation Limited (RCL) — a ₹4,500 crore EPC company in India. The team is small and deliberate, working schema-first inside a real operating company.
Read the originBy 2029, RCL replaces SAP with Fyboard. That's the public bet. If the platform can't run real infrastructure work end-to-end, it isn't ready for anyone.
The long viewWe answer everything that lands in our inbox — usually within a working day. Build context with us; it sharpens what we ship.
Fyboard is in invite-only beta. We're growing deliberately, proving quality with every user before scaling. If that's the kind of thing you'd want to build on, we'd like to hear from you.