Responsible AI
Human accountability, bounded actions, evaluation, and rollback.
Government of Canada registered supplier
Senior product and engineering support for accountable public-sector software.
Amidship is a Canadian, principal-led firm that helps public-sector teams shape, prototype, architect, integrate, and evaluate software where AI or complex workflows are part of the mandate.
Best fit
A senior technical partner when the mandate is still taking shape.
Amidship is best suited to bounded mandates where product judgment, architecture, implementation, and evaluation need to stay closely connected. The firm was founded in 2015 and is based in Pickering, Ontario. Supplier registration details are available during procurement.
AI-enabled workflows
Identify a bounded workflow, define where AI belongs, and move it toward safe operation.
Prototypes and service design
Turn policy or service ambiguity into testable software and measurable acceptance criteria.
Architecture and integration
Connect new intelligence to existing applications, APIs, data, permissions, and operating constraints.
Evaluation and governance
Design action boundaries, human review, observability, evaluation, escalation, and rollback into the system.
Principal-led delivery
One accountable senior lead from discovery through review.
Rida leads discovery, architecture, consequential technical decisions, and final review. Scope-specific specialists can join with defined responsibilities, access, and review paths.
01
Frame
Mandate, users, workflow, constraints
02
Design
Architecture, controls, evidence plan
03
Build + evaluate
Software, integration, tests, review
04
Hand over
Documentation, decisions, next steps
Evidence and trust
Clear attribution. Inspectable technical work. Controls built into delivery.
Amidship corporate work, Rida’s key-person experience, and open-source product R&D are presented separately so evaluators can understand exactly what each item demonstrates.
Security
Least privilege, separated environments, secrets discipline, and third-party controls.
Accessibility
Semantic structure, keyboard access, visible focus, contrast, and testing.
Procurement and partnering
Discuss a bounded mandate or teaming opportunity.
Contact [email protected]
Include the mandate, procurement context, expected role, and any timing or security constraints already known.