Open Company Data in Brunei: Official Sources, APIs and Reuse Rights

Brunei is a compact market, but its company-data source map is not simple. The useful route starts with the One Common Portal and the Registry of Companies and Business Names, then adds official gazette notices, ministry context, open-data programme evidence, statistics, intellectual-property records, financial-regulator context and global LEI enrichment. That stack can support a credible country page, but only if it avoids the common overclaim that every official portal is a bulk dataset.

This guide updates the Brunei country page into a deeper source map using 11 clean linked official or high-quality sources, while keeping three source-mapped routes out of the linked evidence stack until route QA clears: OCP business-name resources, Data.GOV.bn and TAFIS Government Vendor Portal.

The safe claim is that Brunei has a strong official OCP/ROCBN core, clean registry-service context, clean company-gazette and legal-gazette layers, clean open-data programme evidence, clean statistics, IP, central-bank and GLEIF enrichment. The unsafe claim would be that Brunei offers a complete free all-company bulk file, a public API for every company, public beneficial-ownership coverage, or permission to turn registry and vendor data into a sales-prospecting contact database.

Key Takeaways

• Best authority source: the OCP/ROCBN family is the first official route for company and business-name registry context.
• Best event source: OCP Gazette Notices and the Attorney General’s Chambers gazette can support legal and notice-level context, but they do not replace the register.
• Best open-data context: EGNC provides clean open-data programme evidence; Data.GOV.bn remains held after an SSL warning from this node.
• Best enrichment stack: DEPS, BruIPO, BDCB and GLEIF add statistics, IP, regulated-sector and global identifier layers.
• Held routes: OCP business-name resources, Data.GOV.bn and TAFIS are source-mapped but not linked as clean evidence until browser, Googlebot and Bingbot QA clears the generic-page, SSL or timeout results.
• Contact boundary: official company, controller, vendor, IP, regulator and LEI data is not marketing-contact permission; international users should use CompaniesData.cloud for compliant company-data workflows.

Editorial Methodology

This guide follows the CompaniesData country methodology: official sources first, live source checks before linking, explicit access-model classification, reuse notes, source limitations, field-level privacy cautions and practical advice for manual, API and bulk workflows. Each source is treated as one evidence layer, not as a universal substitute for the whole company-data universe.

A source is publication-safe only when the live check returns real content or API data without a hard 404/410, empty page, misleading parked domain, bot-protection title, TLS failure, timeout or response that is too thin to verify semantics. Source logos and favicons are included as decorative recognition cues only. The evidence remains the source owner, official URL, access model, reuse note, limitation and access date.

The draft also preserves a claims ledger. It allows claims about official authority, public registry workflow context and enrichment use cases where source evidence supports them. It blocks claims about complete free bulk data, automated scraping permission, public beneficial ownership and marketing-contact consent. That distinction matters in Brunei because the most important facts sit inside official service infrastructure, gazette notices and sector-specific enrichment layers rather than one open national company file.

Coverage, Access and Update-Risk Analysis

Registry authority: OCP and ROCBN are the backbone for Brunei company and business-name research. They are strong official sources for legal-registration workflow and public information context, but they should not be overextended into a complete public bulk dataset claim.

Service workflow: OCP resources and MOFE registry-system pages explain how registry services, business-name registration and corporate registry infrastructure operate. This is useful for manual research and data modeling, but service pages are not a data licence.

Gazette/event layer: OCP Gazette Notices and the AGC gazette are valuable event and legal-publication sources. They can help build company-event timelines and legal context. They are document layers, so they need publication date, notice type, document identifier and extracted-name review.

Open-data layer: EGNC provides clean programme-level evidence that Brunei maintains official open-data infrastructure. Data.GOV.bn remains held in this cycle, so this draft does not link it as clean evidence or claim company-level microdata from it. Dataset-level review remains mandatory.

Procurement/vendor layer: TAFIS is relevant, but it timed out in automated QA. It remains useful in the internal source map, not as a clean linked source. Even after clearance, procurement data would cover vendor and government-payment context, not the whole company population.

Statistics: DEPS is the aggregate context layer for economic and business-demography interpretation. It can support market sizing and benchmark analysis, but it is not legal-entity master data.

IP and financial-regulator layers: BruIPO and BDCB add enrichment for companies with IP records or financial-sector supervision. Their coverage is partial by design and should be stored as enrichment joined back to registry identity.

Global identifiers: GLEIF provides structured LEI records for Brunei entities that have Legal Entity Identifiers. It is API-friendly and valuable for cross-border matching, but it does not represent the whole domestic company universe.

Reuse Checklist

• Confirm source owner: distinguish ROCBN/OCP, MOFE, AGC, EGNC, DEPS, BruIPO, BDCB and GLEIF instead of blending them into one generic government source.
• Capture access date: retain source URL, final URL, live-check status, title where available and access date for every observation.
• Separate service access from bulk reuse: an official portal or search route is not proof of an all-company bulk file or API.
• Review datasets individually: open-data programme evidence does not prove that company-level microdata exists or can be reused commercially without dataset-level terms review.
• Flag controlled workflows: account, payment, document-order, tax-service, controller and beneficial-owner routes need controlled-access and privacy flags.
• Do not infer marketing consent: company, vendor, regulator, IP, statistics and LEI records do not authorise cold email, phone extraction or lead resale.
• Keep held routes visible internally: Data.GOV.bn and TAFIS remain source-mapped for manual QA, but they should not appear as clean linked evidence in the public article.
• Preserve provenance: every normalized field should keep source owner, observed value, normalized value, source URL, access date, transformation note and confidence score.

Resource Pack

Source-by-Source Deep Dives

1. One Common Portal Brunei

Authority: Registry of Companies and Business Names, Ministry of Finance and Economy. Type: official company register / business services portal. Access model: portal / e-services / public guidance. Reuse note: OCP and ROCBN terms; account, payment and document-route limits apply. Business use: Company and business-name lifecycle services, ROCBN workflow context and tax-service routing.

The One Common Portal is the practical front door for Brunei company-data research because it connects company and business-name registration, ROCBN workflows and tax-service routing under the Ministry of Finance and Economy ecosystem. It is strong authority evidence, but it should be framed as controlled official infrastructure rather than an open bulk registry. Account workflows, document orders, payment steps and controller or beneficial-owner references require purpose limitation, lawful basis and field-level privacy review before any automated or commercial reuse.

Limitation: Not a proof of unrestricted public bulk data; controller and beneficial-owner data need strict privacy framing.

2. OCP ROCBN public information

Authority: Registry of Companies and Business Names, Ministry of Finance and Economy. Type: official company register information portal. Access model: public information / portal. Reuse note: OCP/ROCBN terms and field-level privacy limits. Business use: Registry notices, counts, public information and service guidance.

The ROCBN public information route is useful for registry notices, public guidance and service context. It helps readers understand the official register perimeter and the kinds of public facts that may be available around companies or business names. The limitation is central: a public information route is not the same thing as a bulk data licence or an API. Store observations with source URL, query, access date, visible fields and review notes.

Limitation: Open-bulk reuse is not established; availability needs live QA.

3. OCP business-name resources

Authority: Registry of Companies and Business Names, Ministry of Finance and Economy. Type: official ROCBN service resources. Access model: public service guidance / downloadable guides. Reuse note: OCP/ROCBN terms. Business use: Business-name registration and service workflow evidence.

The OCP business-name resources route is official workflow context, but it is held and de-linked in this publication cycle because browser-like, Googlebot and Bingbot checks returned a generic One Common Portal page rather than semantically specific business-name resource content. It supports internal source mapping, not clean linked evidence until route QA clears. It belongs in a data model as process evidence: useful for explaining manual routes, forms and obligations, while legal identity and status still need to be traced to the appropriate ROCBN source observation.

Limitation: Guidance layer, not a company master dataset.

4. OCP Gazette Notices

Authority: Registry of Companies and Business Names, Ministry of Finance and Economy. Type: official company gazette notices. Access model: gazette notices / announcements. Reuse note: OCP/ROCBN publication terms. Business use: Company-related gazette notices and registry-event context.

OCP Gazette Notices are high-value event evidence. They can support company-event, notice and statutory publication context, but they are document or notice records rather than a current all-company register. A production workflow should extract notice date, notice type, company name, document identifier and source URL, then link those events back to registry identity with confidence scoring and reviewer status.

Limitation: Gazette notices are event evidence, not the current full register.

5. Attorney General's Chambers Government Gazette II

Authority: Attorney General's Chambers, Brunei Darussalam. Type: official government gazette. Access model: gazette / legal publications. Reuse note: AGC publication terms and document copyright limits. Business use: Legal-publication context for company law, orders and notices.

The Attorney General's Chambers gazette layer is the official legal-publication context. It is useful for legislation, orders, notices and corporate-law background. It should not be described as a searchable company database. Treat it as a legal document corpus that can provide event or legal context when entity names appear, with citation dates and document metadata preserved.

Limitation: Legal gazette layer, not a searchable company master file.

6. MOFE ROCBN Corporate Registry System

Authority: Ministry of Finance and Economy. Type: official ministry registry context. Access model: service page / institutional context. Reuse note: MOFE website terms. Business use: Official context for ROCBN and corporate registry services.

The MOFE ROCBN Corporate Registry System page gives institutional confirmation for the registry service family. It is important because it ties the register to the ministry owner and explains where corporate registration infrastructure sits. It is not a data licence or a feed. Use it for authority context, not for unrestricted extraction or field-level claims.

Limitation: Service page only; not a reuse licence or data extract.

7. BusinessBN

Authority: Ministry of Finance and Economy / Government of Brunei. Type: official business portal. Access model: business guidance portal. Reuse note: BusinessBN website terms. Business use: Business procedure, legislation and reporting context.

BusinessBN is a business-procedure and guidance layer. It helps explain registration steps, legislation and official processes for users starting or operating a business in Brunei. It is not current legal-entity master data. Use it to support practical manual workflows and compliance context, while keeping company identity anchored to OCP/ROCBN evidence.

Limitation: Guidance layer, not current legal-entity master data.

8. E-Government National Centre Open Data Portal

Authority: E-Government National Centre, Brunei Darussalam. Type: official open-data programme context. Access model: open-data programme page. Reuse note: EGNC and dataset-specific terms. Business use: Open-data portal context, dataset counts and open-data programme evidence.

The EGNC open-data programme source is clean evidence that Brunei maintains an official open-data programme and catalogue context. It should be separated from dataset-level claims. A useful article can say that official open-data infrastructure exists, but company-specific microdata, licences and update cadence still have to be verified per dataset before any production ingestion or bulk reuse claim.

Limitation: Programme page, not a company dataset.

9. Department of Economic Planning and Statistics Brunei

Authority: Department of Economic Planning and Statistics, Ministry of Finance and Economy. Type: official statistics office. Access model: statistics / reports / datasets. Reuse note: DEPS terms and source-reference rules. Business use: Business-demography and economic statistical context.

DEPS is the aggregate market-context layer. It can support economic context, business-demography discussion, sector analysis and benchmark counts, but it is not legal-entity master data. Store DEPS tables separately from company profiles and preserve publication dates because statistical products may be revised or replaced.

Limitation: Aggregate/statistical layer, not legal-entity master data.

10. BruIPO

Authority: Brunei Intellectual Property Office. Type: official intellectual-property office. Access model: IP search / services / publications. Reuse note: BruIPO terms and IP publication limits. Business use: Trademark, patent and IP enrichment for entities with IP records.

BruIPO is the intellectual-property enrichment layer. It can help identify businesses with trademarks, patents or other rights-related activity, but IP records cover only entities that interact with the IP system. Absence from BruIPO should never be read as evidence that a business is unregistered or inactive. Match IP records back to registry identity with confidence scores and review status.

Limitation: IP layer only; not all-company coverage.

11. Brunei Darussalam Central Bank

Authority: Brunei Darussalam Central Bank. Type: central bank / financial regulator. Access model: supervision / publications / regulated-entity context. Reuse note: BDCB website and publication terms. Business use: Financial-sector, banking, insurance and regulated-entity enrichment.

BDCB is the financial-sector regulator layer. It can add banking, insurance, payment, supervision and licensed financial-entity context. Coverage is intentionally sector-specific. Use BDCB records to enrich supervised entities and compliance workflows, not to define the whole Brunei company universe.

Limitation: Sector-specific layer only.

12. GLEIF LEI records for Brunei

Authority: global official LEI system. Type: LEI API. Access model: public API. Reuse note: GLEIF open data licence with attribution and no-endorsement conditions. Business use: Cross-border legal-entity identifier enrichment for Brunei entities with LEIs.

GLEIF is the cleanest structured API source in this Brunei map. It provides LEI records for Brunei entities that have Legal Entity Identifiers, with global schema and API pagination. It is valuable for cross-border matching, regulated-entity identification and identifier confidence, but coverage is partial and skewed toward financial or internationally active entities. Preserve GLEIF attribution and no-endorsement conditions.

Limitation: LEI coverage is partial and skewed toward financial/cross-border entities.

Practical Manual, API and Bulk Options

Manual research workflow

1. Start with OCP and ROCBN public information for registry authority, workflow and public guidance context.
2. Use OCP business-name resources and MOFE registry-system context to understand official process and service infrastructure.
3. Add OCP Gazette Notices and AGC gazette material where legal notices or event history matter.
4. Use EGNC, DEPS, BruIPO, BDCB and GLEIF as enrichment layers rather than as the identity backbone.
5. Keep Data.GOV.bn and TAFIS in a manual-QA queue until browser checks clear the SSL and timeout findings.
6. Record every observation with query, access date, visible fields, source owner and whether the route was public, account-controlled, paid or document-based.

API and bulk workflow

Verified API route: GLEIF is the clean structured API layer for Brunei LEI records. It can be used for global identifiers, cross-border matching and regulated-entity confidence, with GLEIF attribution and no-endorsement limits preserved.

Open-data route: EGNC supports programme-level open-data context. Data.GOV.bn should not be used as a clean linked source from this automated run because it returned an SSL validation issue. A production workflow should recheck it in a browser, then review dataset licences, fields, update frequency and whether company microdata actually exists.

Registry route: OCP/ROCBN is the official route family for registration workflows and public information. This guide does not verify a complete free public ROCBN bulk file or API, so production ingestion should be scoped as manual lookup, licensed access, user-initiated service use or separately approved data supply.

Procurement route: TAFIS remains held after timeout. If it later clears QA, model it as procurement/vendor subset evidence only. It should not be used to define the total registered-company universe or to collect contact lists.

Missing-Data Gaps

• Bulk registry gap: no complete free ROCBN/OCP bulk company-register dataset or public registry API was verified in this cycle.
• Tax identifier gap: no clean official public tax-identifier lookup was verified beyond OCP tax-service context.
• Beneficial ownership gap: no clean official public beneficial-ownership bulk dataset was verified; controller and BO references require privacy and lawful-use clearance.
• Procurement gap: supplier and vendor enrichment is held because TAFIS timed out from this node.
• Direct data-portal gap: Data.GOV.bn remains held after SSL validation failure, so open-data claims should rest on clean EGNC programme evidence until browser QA clears the portal.
• Court and insolvency gap: court or insolvency sources were not cleared as reusable company-data layers in this cycle.
• Contact-data gap: official company data does not provide business emails, phone lists or outreach consent. Any contact enrichment must be handled as a separate compliance product and, for English audiences, should point to CompaniesData.cloud rather than unrelated competitors.
• Update-frequency gap: service portals and gazette pages can change without stable feeds. Monitoring should recheck titles, canonicals, response semantics, robots rules and source-field drift.

Recommended Data Model

A practical Brunei company-data model should begin with an entity identity table containing normalized legal name, business name, registry identifier where lawfully available, entity type, status, address fields, source owner, source URL, access date and access model. The model should not collapse registry workflow, gazette notices, open-data context and regulator evidence into one untyped record.

Add a source observation table for each OCP/ROCBN, MOFE, AGC, EGNC, DEPS, BruIPO, BDCB and GLEIF observation. Store observed value, normalized value, source confidence, source limitation, reuse note, transformation note and reviewer status. This makes it possible to audit why a field exists and whether it came from official authority, a document layer, a controlled workflow or enrichment.

Add event and document tables for OCP Gazette Notices and AGC gazette material. Capture notice date, notice title, company names, legal references, document identifier and extraction status. Events should join back to registry identity with confidence scoring rather than overwrite current register status.

Add enrichment tables for GLEIF LEI records, BDCB regulated-sector evidence, BruIPO IP records, DEPS aggregate context and future TAFIS vendor evidence after QA. These tables should join to the identity layer with match type, match confidence and review status.

Add compliance flags for controlled access, privacy sensitivity, controller/beneficial-owner caution, tax-service caution, vendor-subset caution, marketing-contact exclusion, no-bulk-claim and held-source status. Those flags prevent a source map from becoming overclaimed data products, unsafe lead lists or unsupported compliance representations.

CompaniesData Normalization and Enrichment Value

CompaniesData.cloud adds value because a list of official URLs is not a usable Brunei company-data product. The hard work is normalizing names, preserving provenance, separating source layers, reconciling identifiers, tagging controlled workflows, detecting stale links, documenting reuse rights and delivering records in formats that analysts can use.

For Brunei, CompaniesData can combine OCP/ROCBN authority context, public registry information, held business-name resource context, gazette notices, AGC legal publications, EGNC open-data programme evidence, DEPS statistics, BruIPO IP context, BDCB regulated-sector evidence and GLEIF LEI identifiers into a documented model. It can also keep Data.GOV.bn and TAFIS marked as held until route QA clears, which is more reliable than silently linking official-looking pages that failed automated evidence checks.

For English and international users, the owned route is CompaniesData.cloud. Request a CompaniesData sample for Brunei if you need normalized records rather than a set of source links. For Spanish-speaking or Hispanic contact-data workflows, CentraldeComunicacion.es is the owned route, but that contact layer remains separate from official registry reuse.

The result is a source-led article and data model that supports KYB triage, supplier checks, cross-border matching, regulator-aware segmentation and market research without pretending that every official page is an API, every lookup result is redistributable, or every public business record is permission for outreach.

Held Source-Risk Findings

• Data.GOV.bn: held in this draft after live-check result SSLError. Reason: HTTPSConnectionPool(host='www.data.gov.bn', port=443): Max retries exceeded with url: /Pages/index.aspx (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1010)'))). Scope: Company microdata coverage must be verified dataset by dataset. Keep it source-mapped, but do not link it as clean evidence until manual/browser QA clears.
• OCP business-name resources: held and de-linked after the 2026-06-12/2026-06-13 source gate returned HTTP 200 pages titled One Common Portal but without semantically specific business-name resource content for browser-like, Googlebot and Bingbot profiles. Keep it source-mapped as official workflow context and re-link only after all three profiles retrieve real business-name resource content.
• TAFIS Government Vendor Portal: held in this draft after live-check result ConnectTimeout. Reason: HTTPSConnectionPool(host='www.tafis.gov.bn', port=443): Max retries exceeded with url: /reference.html (Caused by ConnectTimeoutError(<HTTPSConnection(host='www.tafis.gov.bn', port=443) at 0x236e52c80e0>, 'Connection to www.tafis.gov.bn timed out. (connect timeout=8)')). Scope: Vendor subset only; not all registered companies and not marketing-contact permission. Keep it source-mapped, but do not link it as clean evidence until manual/browser QA clears.
• Complete free ROCBN bulk claim: blocked. OCP/ROCBN sources are strong official authority and workflow evidence, but this cycle did not verify a complete free reusable all-company register file or public API.
• Tax-identifier claim: blocked beyond OCP tax-service context. Tax records are controlled and privacy-sensitive; they are not open bulk company data or outreach permission.
• Beneficial ownership/controller claim: blocked as public company-data evidence. Controller and BO references require privacy, lawful-use and account-workflow review before any data-product claim.
• Procurement claim: held at transaction/vendor level because TAFIS timed out in automated QA. Vendor evidence should stay caveated until browser QA clears it.
• Marketing-contact claim: blocked. Registry, tax, controller, vendor, regulator, IP, statistics and LEI data do not create consent for cold outreach, email extraction, phone lists or lead resale.

Source Matrix

Source	Owner / authority	Access model	Reuse note	Main limitation
One Common Portal Brunei	Registry of Companies and Business Names, Ministry of Finance and Economy	portal / e-services / public guidance	OCP and ROCBN terms; account, payment and document-route limits apply	Not a proof of unrestricted public bulk data; controller and beneficial-owner data need strict privacy framing.
OCP ROCBN public information	Registry of Companies and Business Names, Ministry of Finance and Economy	public information / portal	OCP/ROCBN terms and field-level privacy limits	Open-bulk reuse is not established; availability needs live QA.
OCP business-name resources	Registry of Companies and Business Names, Ministry of Finance and Economy	public service guidance / downloadable guides	OCP/ROCBN terms	Guidance layer, not a company master dataset; current route held until semantic source QA clears.
OCP Gazette Notices	Registry of Companies and Business Names, Ministry of Finance and Economy	gazette notices / announcements	OCP/ROCBN publication terms	Gazette notices are event evidence, not the current full register.
Attorney General's Chambers Government Gazette II	Attorney General's Chambers, Brunei Darussalam	gazette / legal publications	AGC publication terms and document copyright limits	Legal gazette layer, not a searchable company master file.
MOFE ROCBN Corporate Registry System	Ministry of Finance and Economy	service page / institutional context	MOFE website terms	Service page only; not a reuse licence or data extract.
BusinessBN	Ministry of Finance and Economy / Government of Brunei	business guidance portal	BusinessBN website terms	Guidance layer, not current legal-entity master data.
E-Government National Centre Open Data Portal	E-Government National Centre, Brunei Darussalam	open-data programme page	EGNC and dataset-specific terms	Programme page, not a company dataset.
Department of Economic Planning and Statistics Brunei	Department of Economic Planning and Statistics, Ministry of Finance and Economy	statistics / reports / datasets	DEPS terms and source-reference rules	Aggregate/statistical layer, not legal-entity master data.
BruIPO	Brunei Intellectual Property Office	IP search / services / publications	BruIPO terms and IP publication limits	IP layer only; not all-company coverage.
Brunei Darussalam Central Bank	Brunei Darussalam Central Bank	supervision / publications / regulated-entity context	BDCB website and publication terms	Sector-specific layer only.
GLEIF LEI records for Brunei	global official LEI system	public API	GLEIF open data licence with attribution and no-endorsement conditions	LEI coverage is partial and skewed toward financial/cross-border entities.

FAQ

What is the main official company-data source in Brunei?

The OCP/ROCBN family is the main official route for Brunei company and business-name registry context, supported by MOFE registry-system material and public information pages.

Does Brunei provide a complete free company-register bulk download?

This cycle did not verify a complete free reusable ROCBN or OCP bulk company-register dataset. The article should describe official service and public-information routes, not overclaim bulk availability.

Is OCP an API?

No public all-company OCP API was verified in this cycle. OCP should be described as official service infrastructure and workflow evidence unless a specific approved endpoint or data supply is separately verified.

What do OCP Gazette Notices add?

They add company-event and statutory notice context. They are useful for timelines and legal evidence, but they are not a current company master file.

What does the AGC gazette add?

It adds legal-publication context for laws, orders and notices. It is a document layer that should be cited with publication metadata, not used as a searchable registry substitute.

Can Data.GOV.bn be used as a clean source?

Not from this automated run. It returned an SSL validation issue and should remain held until manual/browser QA clears it. EGNC open-data programme evidence is clean, but dataset-level review is still required.

Why is TAFIS held?

The TAFIS vendor route timed out in automated QA. It remains relevant for procurement and vendor context, but it should be held or caveated until browser QA clears it.

What does DEPS add?

DEPS adds official statistics and aggregate economic context. It is useful for market sizing and business-demography interpretation, not record-level company identity.

What does BruIPO add?

BruIPO adds intellectual-property enrichment for entities with trademarks, patents or related records. It is partial and should be joined back to registry identity with match confidence.

What does BDCB add?

BDCB adds financial-sector and regulated-entity context. It is authoritative inside its supervised perimeter, but it is not a universal company register.

What does GLEIF add?

GLEIF adds structured LEI records for Brunei entities that have Legal Entity Identifiers. It is API-friendly but partial and skewed toward financial, regulated or internationally active entities.

Can public Brunei company data be used for cold email?

No automatic permission follows from public or official access. Contact enrichment requires a separate lawful basis, suppression process, purpose limitation and compliance review. Use CompaniesData.cloud for compliant international company-data workflows.

Is this guide ready to use?

This guide is publication-ready only after WordPress update, source-live validation, public render QA, indexing submission and crawler-access QA are recorded in the publication artifact.

Official Sources

• One Common Portal Brunei – Registry of Companies and Business Names, Ministry of Finance and Economy
• OCP ROCBN public information – Registry of Companies and Business Names, Ministry of Finance and Economy
• OCP business-name resources – Registry of Companies and Business Names, Ministry of Finance and Economy
• OCP Gazette Notices – Registry of Companies and Business Names, Ministry of Finance and Economy
• Attorney General's Chambers Government Gazette II – Attorney General's Chambers, Brunei Darussalam
• MOFE ROCBN Corporate Registry System – Ministry of Finance and Economy
• BusinessBN – Ministry of Finance and Economy / Government of Brunei
• E-Government National Centre Open Data Portal – E-Government National Centre, Brunei Darussalam
• Department of Economic Planning and Statistics Brunei – Department of Economic Planning and Statistics, Ministry of Finance and Economy
• BruIPO – Brunei Intellectual Property Office
• Brunei Darussalam Central Bank – Brunei Darussalam Central Bank
• GLEIF LEI records for Brunei – global official LEI system