Skip to main content
Fe26Ferrum OS

Less tools. More work.

Move one building project from land to delivery.

Start with land, a brief, or an existing professional model. SUTRA coordinates the next bounded step while Ferrum preserves evidence, revisions, unknowns, and approval authority.

Regional availability

Know the boundary before you start.

Set your country code in the header to see what evidence is still required. Blank means UNKNOWN.

AVAILABLEINDICATIVEPARTIALEXTERNAL_GATEUNAVAILABLE
How this is assessed

Ferrum does not use device or IP location here. Your entry is not persisted, does not create or update a project jurisdiction record, and does not prove regional or regulatory coverage.

Recognized and unrecognized entries are USER_DECLARED / UNVERIFIED until a cited project record and coverage source exist.

Project jurisdiction record

UNAVAILABLE

Jurisdiction not declared — the caller must supply one explicitly before this feature can be evaluated.

Freshness: no coverage timestamp

Evidence and fallback
  • jurisdiction: No jurisdiction was declared for this request.

Fallback: Do not render Project jurisdiction record; show an explicit "not available in your region" state and, if applicable, a way to request coverage.

Regional evidence layers

UNAVAILABLE

Jurisdiction not declared — the caller must supply one explicitly before this feature can be evaluated.

Freshness: no coverage timestamp

Evidence and fallback
  • jurisdiction: No jurisdiction was declared for this request.

Fallback: Do not render Regional evidence layers; show an explicit "not available in your region" state and, if applicable, a way to request coverage.

Regulated conclusions

UNAVAILABLE

Jurisdiction not declared — the caller must supply one explicitly before this feature can be evaluated.

Freshness: no coverage timestamp

Evidence and fallback
  • jurisdiction: No jurisdiction was declared for this request.

Fallback: Do not render Regulated conclusions; show an explicit "not available in your region" state and, if applicable, a way to request coverage.

Local-language support

UNAVAILABLE

Jurisdiction not declared — the caller must supply one explicitly before this feature can be evaluated.

Freshness: no coverage timestamp

Evidence and fallback
  • jurisdiction: No jurisdiction was declared for this request.

Fallback: Do not render Local-language support; show an explicit "not available in your region" state and, if applicable, a way to request coverage.

Connected regional services

UNAVAILABLE

Jurisdiction not declared — the caller must supply one explicitly before this feature can be evaluated.

Freshness: no coverage timestamp

Evidence and fallback
  • jurisdiction: No jurisdiction was declared for this request.

Fallback: Do not render Connected regional services; show an explicit "not available in your region" state and, if applicable, a way to request coverage.

LandIntel · selected product

Is this parcel viable — what does the record say, and what does it allow?

Land buyer/developer deciding whether to buy or build on a specific plot

  • Understand the site

    Check feasibility, zoning, and site risk signals before you commit.

    LandIntel — Land buyer/developer deciding whether to buy or build on a specific plot

Find parcel

Choose a method, then set or look up the location below.

SAMPLE

SAMPLE LOCATION · Bengaluru reference centre — not a parcel.

Selected point 12.97160, 77.59460 · sample reference

Loading 3D map…

Parcel record · sample

Bengaluru Urban

PREVIEW · SAMPLE
ULPIN
KA-BLR-0001-2024
State
Karnataka
Recorded land use
Residential
Zoning verification status
REQUIRES AUTHORITY VERIFICATION

Plot area · all units from one base of 1,200 m²

m²
1,200
sq ft
12,917
cents
29.65
guntha
11.86
ground
5.38
acre
0.2965

Converted with exact constants and rounded for display (m² to 2 decimals, sq ft to 0, cents, guntha, ground to 2 and acre to 4).

ULPIN identifies the parcel. Building use is derived only after the competent planning authority's current zoning record is verified; Ferrum does not offer unrestricted use choices.

Building-type guidance appears after a seeded lookup; none is shown for the sample.

Source: Preview sample — replaced in place by a seeded lookup; not a registry resultFreshness: PREVIEW · sample, not a live recordIndicative

Governed orchestration

Roadmap contract

One revision. Every consequence traced to closure.

Ferrum’s platform promise is a governed chain of project decisions. Common screens alone do not establish coordination; shared evidence, accountable state transitions and controlled approval do.

Current status

Specification visible · end-to-end execution not built

  1. Step 01DesignStudio

    Design revision

    A controlled revision enters the project record.

    Required evidence: Revision ID, author, timestamp and changed geometry

  2. Step 02BOQ Pro

    Affected quantity

    Only quantities touched by the revision are recalculated.

    Required evidence: Measurement basis, before/after quantity and source elements

  3. Step 03Procura

    Procurement hold

    Affected requests and orders are held before commitment.

    Required evidence: Linked line items, supplier status and accountable owner

  4. Step 04BOQ Pro · InvestFlow

    Cost impact

    The commercial effect is recomputed without hiding uncertainty.

    Required evidence: Rate source, variance, contingency and confidence status

  5. Step 05Ferrum Projects

    Site instruction

    An approved instruction reaches the responsible site team.

    Required evidence: Instruction revision, approver, recipients and acknowledgement

  6. Step 06Ferrum Projects

    Acceptance evidence

    Completion is supported by inspection evidence.

    Required evidence: Checklist, photos, test records, date and responsible reviewer

  7. Step 07Ferrum Projects

    Controlled closure

    The chain closes only after every hold and acceptance condition is resolved.

    Required evidence: Closure authority, linked records and immutable audit trail

AI accountability record

Every recommendation must answer six questions.

  • What event triggered the AI?
  • What evidence did it inspect?
  • What recommendation did it produce?
  • Who retained approval authority?
  • What downstream records changed?
  • How can the decision be audited?

How it works

From plot to delivery in five steps

A clear path from your first land lookup through design, cost, and delivery.

Step 1 of 5

Highlighted product

LandIntel

LIVE

ULPIN lookup (live)

LIVE

Look up one of three seeded ULPIN records through the D1-backed lookup, with a city-reference map and explicit provenance.

Interactive preview map (live)

LIVE

View the selected lookup result or chosen coordinates on an OpenStreetMap reference map. It does not assert an official parcel boundary.

Next step appears automatically after 7 seconds.

Explore LandIntel