Submission declined on 6 June 2026 by Bobby Cohn (talk). This draft's references do not show that the subject meets Wikipedia's criteria for inclusion for organizations and companies. The draft requires multiple published secondary sources that: provide significant coverage: discuss the subject in detail, excluding routine coverage like product launches, staff appointments, or financial reports and listings in databases or listicles; are reliable: from reputable outlets with editorial oversight; are independent: not connected to the subject, such as press releases, the subject's own website, or sponsored content. Please add references that meet all three of these criteria. If none exist, the subject is not yet suitable for Wikipedia. This draft reads like an advertisement. Wikipedia is an encyclopedia, not a platform for promotion or marketing. Drafts that are exclusively promotional may be deleted without notice. Wikipedia articles must be written neutrally in a formal, impersonal, and dispassionate way. They should not read like a blog post, advertisement, or fan page. Rewrite the draft to remove: promotional language: see Words to watch; personal commentary: opinions or direct addresses to the reader; informal language. Instead, only summarize in your own words a range of independent, reliable, published sources that discuss the subject. If you have a conflict of interest (e.g. you are the subject, an employee, or a relative) or are being paid to edit, you must disclose this to comply with Wikipedia's Terms of Use. If you would like to continue working on the submission, click on the "Edit" tab at the top of the window. If you have not resolved the issues listed above, your draft will be declined again and potentially deleted. If you need extra help, please ask us a question at the AfC Help Desk or get live help from experienced editors. Please do not remove reviewer comments or this notice until the submission is accepted. Where to get help If you need help editing or submitting your draft, please ask us a question at the AfC Help Desk or get live help from experienced editors. These venues are only for help with editing and the submission process, not to get reviews. If you need feedback on your draft, or if the review is taking a lot of time, you can try asking for help on the talk page of a relevant WikiProject. Some WikiProjects are more active than others so a speedy reply is not guaranteed. How to improve a draft Wikipedia:Contributing to Wikipedia – a basic overview on how to edit Wikipedia. Help:Wikitext – how to use the markup Help:Referencing for beginners – how to include references Wikipedia:Article development – how to develop your article Wikipedia:Writing better articles – how to improve your article Wikipedia:Verifiability – make sure your article includes reliable third-party sources You can also browse Wikipedia:Featured articles and Wikipedia:Good articles to find examples of Wikipedia's best writing on topics similar to your proposed article. Improving your odds of a speedy review To improve your odds of a faster review, tag your draft with relevant WikiProject tags using the button below. This will let reviewers know a new draft has been submitted in their area of interest. For instance, if you wrote about a female astronomer, you would want to add the Biography, Astronomy, and Women scientists tags. Add tags to your draft Editor resources Easy tools: Citation bot (help) | Advanced: Fix bare URLs Declined by Bobby Cohn 3 hours ago. Last edited by AnomieBOT 3 hours ago. Reviewer: Inform author. Resubmit Please note that if the issues are not fixed, the draft will be declined again.

• Comment: This draft is written from the viewpoint of the company, focusing on what the company says about itself. Corporate notability is based on what independent reliable sources have written about the subject.
  Not every business corporation is notable, and this draft does not establish corporate notability. You may ask for advice about corporate notability at the Teahouse.Thank you. Bobby Cohn 🍁 (talk) 11:20, 6 June 2026 (UTC)

BrightAccess (registered as brightaccess.ca) is a Canadian financial and educational technology platform that provides artificial intelligence-powered scholarship administration services.^[1] Founded in 2025, it serves foundations, charitable organizations, review panels, and student applicants across Canada. The platform operates on a software-as-a-service (SaaS) model.

The platform provides centralized infrastructure for managing the entire scholarship lifecycle: from intake form design to candidate matchmaking, rubric assessments, document authenticity checks, void cheque scanning, and automated disbursements.^[2]

Unlike standard global grant tools, BrightAccess is designed specifically for the Canadian regulatory framework, offering built-in T4A tax receipt generation, CRA (Canada Revenue Agency) compliance logging, and provincial residency validations.^[2]

Prior to the establishment of digital portals, scholarship administration in Canadian educational foundations relied heavily on manual data entry, physical paper portfolios, and spreadsheet matrices. Reviewers experienced high score variance and bias. Administrative teams dedicated hundreds of labor-hours each fiscal cycle checking compliance with residency and educational enrollment proofs.

In 2025, software engineers and foundation consultants initialized the BrightAccess framework. The platform aimed to automate routine document validation tasks while maintaining strict compliance with the Canada Revenue Agency rules regarding educational funding distributions.^[2]

By 2026, the codebase evolved to incorporate advanced language models (LLMs) and computer vision modules, enabling automated processing of receipts, transcripts, and financial verification documents without compromising security.^[3]

The BrightAccess dashboard provides specialized panels for four distinct roles: Students, Foundation Admins, Reviewers, and Accountants. Key sub-features include:

Foundation Admins configure rubric criteria for individual scholarships. The backend implements the AI_API_KEY parameter to call Gemini models (specifically gemini-3.1-flash-lite), compiling structured JSON feedback. The system generates initial alignment scores, grammatical reports, and key theme tags. These reports assist human reviewers rather than replacing final human judgment.^[3]

To prevent fraudulent educational credentials and residency claims, the platform automatically routes uploaded transcript PDFs and identification cards to document verification layers. It utilizes vision models to assess document metadata, text layers, and scanning artifacts to generate risk indicators.

Upon approval, students upload void cheques for EFT/direct deposit. The platform parses direct deposit variables (transit, institution, and account numbers) using Optical Character Recognition (OCR). This system matches direct deposit details with the registered user profile to prevent cross-account routing errors before funds are dispatched by the accountant.

Asta is an integrated chat application available directly within the foundation dashboard. Using a vector search engine (pgvector), Asta references historical scholarship programs, applicant logs, and support queries to provide admins with instant statistical insights and report drafts.

BrightAccess is built using a decoupled service-oriented architecture:

• Client Interface: Next.js 15, React, and Tailwind CSS.
• Application Server: NestJS, Node.js, and TypeScript using a controller/service/module architecture.
• Primary Database: PostgreSQL database using TypeORM mapping.
• Worker Queue: BullMQ and Redis for processing email dispatches, template compiling, and batch report processing.
• Cloud Storage: AWS S3 for secure document handling via presigned client upload links.
• Telemetry: Sentry SDK for real-time error capturing and performance monitoring.

Due to the sensitivity of personal student records, GPA transcripts, and financial void cheques, the platform enforces several security protocols:

• Tiered Rate Limiting: Backed by @nestjs/throttler, request limits are enforced per IP address across three sliding windows: short-burst protection (10 req/sec), medium traffic control (50 req/10s), and long sustained limiting (200 req/min). Specialized throttlers protect Firebase authentication and AI endpoints.^[4]
• Security Headers: Helmet middleware sets strict headers including X-Frame-Options: DENY to prevent clickjacking, and X-Content-Type-Options: nosniff to prevent MIME sniffing.^[4]
• CORS Restrictions: The backend verifies and permits requests from whitelisted subdomains (e.g., *.brightaccess.ca), blocking and logging violations in production.
• Firebase Custom Roles: Authentication tokens carry Firebase UID claims. A custom NestJS RolesGuard extracts the request claims and resolves the database user details (req.dbUser) containing verified role status.^[1]

• Educational technology
• Software as a service
• Canada Revenue Agency

Category:Educational technology companies of Canada Category:Financial technology companies of Canada Category:Software companies established in 2025 Category:SaaS companies