Skip to content

Locations · Lexington, KY

Web, Mobile and AI Builds for Lexington

OlDevs designs and builds software for Lexington organisations in agriculture, manufacturing, health care and research. We run the work from Vancouver over video, in your hours, and you own every line of code and every account at the end.

Remote from Vancouver, on-site when useful Weekly working demos Reply within one business day

Illustrative product interface — not client data.

Lexington, in short

Yes, Lexington organisations can hire OlDevs.The studio is based in Vancouver, British Columbia, and engagements run remotely, with a trip to Kentucky when a build calls for one, and Lexington sits in Eastern Time, three hours ahead of us, so our morning is your early afternoon and that window carries the meetings. We handle web apps, Android and iOS apps, web development, full-stack engineering, AI development and performance marketing.

Key facts

01Location
Lexington, Kentucky, United States
02Time zone
Eastern Time, which is three hours ahead of Pacific time in Vancouver
03Working hours overlap
Vancouver mornings meet Lexington afternoons, giving roughly five shared hours each day from around noon your time, and we schedule live sessions there
04Privacy law
The Kentucky Consumer Data Protection Act, in force from January 2026
05Accessibility
Public-facing sites face ADA Title III litigation risk; the 2024 ADA Title II rule holds state and local government web content to WCAG 2.1 AA, with an April 2026 deadline for populations of 50,000 and over and April 2027 for the rest; federal work falls under Section 508; we deliver WCAG 2.2 AA
06Languages
English

Built for Kentucky

What Lexington projects need us to get right.

The local rules and realities we design for from the first call.

01

The Kentucky Consumer Data Protection Act

Kentucky's Consumer Data Protection Act came into force in January 2026, which moves consent, purpose and resident data requests into the build rather than a policy page. We keep collection narrow, record why each field exists, and make deletion something your staff can actually run.

KCDPA · Consent · Deletion

02

WCAG 2.2 AA on every page

United States sites that face the public carry ADA Title III litigation risk, and the 2024 ADA Title II rule requires WCAG 2.1 AA for state and local government content on an April 2026 and April 2027 timetable set by population size. Lexington work is tested against WCAG 2.2 AA.

WCAG 2.2 AA · ADA Title II

03

Clear English for mixed audiences

Lexington operates in English across farms, plants, clinics and campuses, so a single site often has to speak to a veterinarian, a buyer and a family in the same week. We write each path in the language its reader uses. French delivery is available if a market needs it.

Content · Audience · EN/FR

04

United States hosting, accounts in your name

We host Lexington projects in United States regions so records stay close to the organisations that own them, and we write down exactly where the database, media, backups and logs sit. Every hosting, domain and analytics account is registered to your organisation.

Hosting · Data residency · Ownership

Sectors

Who we work with in Lexington.

Equine industry and agriculture

Farms, sales agencies and equine services need catalogues, records and booking that hold up during a sale week. We build searchable listings, pedigree and health record views, and mobile pages that load on a barn connection.

Advanced manufacturing

Manufacturers around Lexington want quoting, scheduling and quality reporting joined to systems already in place. We integrate through APIs, keep screens usable in gloves and poor light, and hand over documentation your own team can maintain.

Health care

Providers need scheduling, intake and follow-up that keep protected information away from advertising tools. We map each patient journey, remove the steps that cause drop-off, and test everything with a keyboard and a screen reader before release.

Education and research

Universities, colleges and research groups need program pages, application flows and internal portals that many departments can update. We build a content model with clear ownership so pages stay accurate without a developer in the loop.

Process

Working with OlDevs from Lexington.

  1. Discover

    We open with a working session in your Lexington afternoon covering goals, users, systems and success measures, and send back a written scope you can share with the people who approve it.

  2. Design

    Structure and interface come first, drawn and reviewed while opinions are cheap to act on. Accessibility, content ownership and data questions get settled here rather than during the build.

  3. Build

    Each week ends with something you can click, plus a plain note on progress and blockers. One accountable team stays with the project instead of rotating people through it.

  4. Launch

    Going live is a checklist we run together: United States hosting in your name, monitoring and analytics confirmed, content proofed, and a tested route back if anything misbehaves.

  5. Grow

    We stay close after release, reading behaviour, improving speed and accessibility, and running SEO, paid search, paid social, email and CRO programs for clients who want them.

FAQ

Lexington — questions we hear first.

No, and we will not imply otherwise. The studio is in Vancouver, British Columbia, and Lexington projects are delivered remotely with calls in Eastern Time, weekly demos and written records of every decision. We travel to Kentucky when a workshop, a site visit or a launch is better done face to face.

In force since January 2026, it makes consent, stated purpose and resident data requests part of the design work. Practically, forms ask for less, consent is recorded rather than assumed, retention has an owner, and staff have a screen for handling requests. Your legal advisers still interpret the statute for your circumstances.

Rarely, because we plan around it. Lexington runs three hours ahead of Vancouver, and the shared window is your afternoon against our morning. Decisions and demos go there, written updates cover the rest, and every enquiry gets a reply within one business day so nothing waits overnight for no reason.

Yes. We pick a United States region during discovery so Lexington users get short round trips, then document where the database, uploaded files, backups and logs actually live. Accounts sit in your organisation's name from the beginning, which means the infrastructure never depends on our relationship continuing.

We do. That work usually means catalogues, records and booking tools that have to behave during a sale or a busy season, often on patchy rural connections. We design for slow networks and small screens first, then add the richer desktop view for office staff who need the full picture.

Within one business day. The first reply is a real response with questions about scope, users and timing, not an automated acknowledgement. From there we book a call in your Lexington afternoon, and if the project is not a good fit for a Vancouver studio we will say so plainly.

Still have a question? Ask us when you request a quote

Let’s connect

Tell us about your Lexington project.

We’ll reply within one business day, in your working hours, with next steps and a tailored quote — no obligation.

We’ll only use your details to prepare your quote. No lists, no spam.

Call us Request a quote