Enterprise Software Development Company in Edmonton

Alberta's access and privacy regime for public bodies was split into two statutes: the Access to Information Act, which governs the right of access to records, and the Protection of Privacy Act, which governs how public bodies collect, use, disclose and protect personal information. The Office of the Information and Privacy Commissioner of Alberta oversees both alongside the Freedom of Information and Protection of Privacy Act, the Health Information Act, the Personal Information Protection Act and the Access to Motor Vehicle Information Regulation, so the Commissioner's office is a single regulator across a fragmented statutory landscape. For system design this matters in four concrete ways. Records have to be classifiable and retrievable in a form that survives an access request, including audit logs and system-generated records people forget are records. Collection has to be tied to a stated authority and purpose, recorded at the field level. Disclosure paths, including any transfer to a service provider or another jurisdiction, have to be documented before they are built. And privacy incident handling needs an actual workflow rather than an email address. We build the records and retention design during discovery and validate it with your access and privacy office before architecture is fixed.

Quoted in Canadian dollars against a signed statement of work. A discovery and working prototype engagement, covering legislative and records analysis, service design, a clickable or functional prototype and a costed delivery plan you can take to a budget cycle, typically runs CAD 60,000 to 150,000 over eight to fourteen weeks, and it is the single best way to avoid a failed procurement. A production platform serving a department or a business line, including integration to identity and two or three systems of record, accessibility conformance, security testing and a real handover, typically runs CAD 300,000 to 900,000. A multi-year legacy replacement program moving a mainframe, Oracle Forms or IBM i estate onto a modern stack by strangler pattern, with parallel running and staged cutover, runs CAD 900,000 to 3,000,000 and up depending on how many business rules are undocumented, which is the variable nobody can price up front. Edmonton rates run below Toronto and Vancouver, and for a public body that difference is real budget rather than margin. We are also willing to say when a packaged product is the right answer and custom development is not.

Alberta public bodies procure under the Canadian Free Trade Agreement, which opens covered procurements to suppliers across Canada, and under the New West Partnership Trade Agreement between Alberta, British Columbia, Saskatchewan and Manitoba, which adds further obligations in the western market. Above the applicable thresholds, which the agreements set and adjust periodically, procurements must be openly tendered on an electronic tendering system, evaluation criteria must be published in advance and applied as published, and there are limited and specific grounds for limited tendering. The practical consequence for a buyer is that the requirements document does most of the work, because you cannot change the evaluation basis afterward. Where we can help before a tender exists, we do it as a paid discovery engagement scoped so it does not disqualify us from bidding the build, and we say so plainly rather than leaving a conflict for procurement to discover. Where a tender is already published we respond to it as written. We are headquartered in Alberta, which satisfies local presence questions honestly, and we do not claim offices we do not have.

Alberta has no provincial accessibility statute of the kind Ontario has in the Accessibility for Ontarians with Disabilities Act, so the obligation comes from other directions. The federal Accessible Canada Act, in force since 2019, applies to federally regulated entities. Human rights obligations apply to everyone. Public sector procurement in this province routinely requires conformance with the Web Content Accessibility Guidelines at level AA, and Accessibility Standards Canada has adopted the EN 301 549 information and communication technology standard as a Canadian standard, which is where larger requirements documents increasingly point. In practice we build to WCAG 2.1 level AA as the floor and treat 2.2 additions as expected. How matters more than which. We build accessibility into the component library so it is inherited rather than retrofitted, we test in every sprint with keyboard-only navigation and a screen reader rather than relying on automated scanning that catches roughly a third of real issues, and we include people who use assistive technology in usability testing where the client can support it. Conformance is documented in an accessibility conformance report at handover.

By never taking it offline. Big-bang replacement is why public sector modernization has the reputation it has, and it fails for a predictable reason: the old system encodes years of undocumented business rules, and you find them at cutover. We use the strangler pattern. First we put a facade in front of the legacy system so consumers stop calling it directly. Then we extract capability by capability, standing up a new service, running it in parallel against production traffic in shadow mode, comparing outputs against the legacy result, and only cutting over that capability once the comparison is clean for a sustained period. Data is synchronized both ways during the transition, with a clearly designated system of record for each entity at each stage so nobody has to guess. Business rule archaeology runs alongside: reading COBOL, Oracle Forms or PowerBuilder source, interviewing the staff who know the exceptions, and writing rules down as testable specifications before reimplementing them. This takes longer on paper than a rewrite and finishes sooner in practice, because the risk is spread across many small reversible steps instead of concentrated in one weekend that cannot be reversed.

It means the vendor is local in the way procurement and delivery actually care about. Our head office is in Edmonton, so workshops with your access and privacy office, service design sessions with front-line staff, and security architecture reviews happen in person. We hire from the University of Alberta, NAIT and MacEwan, so the people on your project live here and are still reachable next year. It also means the accountable work is not handed offshore: analysis, architecture, security and client-facing delivery sit in Edmonton on Mountain Time, so the person who wrote the privacy impact assessment is the person in the room when it is challenged. Chandigarh sits roughly half a day around the clock and covers build throughput, regression testing and long-running migration overnight. We say plainly which work happens where, because a public body will be asked that question during evaluation and a vague answer is worse than an offshore one. The firm dates to 2018, counts 500 or more delivered projects, and carries more than 200 engineers across its Edmonton and Chandigarh offices. You can reach us at +1 (403) 604-8692 and meet the people who would actually do the work.