Frequently asked questions

We are an LMS engineering partner: we build, customize, integrate, migrate, optimize and maintain learning platforms across Moodle, WordPress LMS, Open edX, Canvas, SaaS LMSs and custom platforms.

No - that is the point of "all-in-one". We recommend the platform that fits your organization, then build on it.

Engineers. The people scoping and building your project are the people you speak with, from the first call to launch.

We work remotely with clients in different regions and schedule regular calls within your business hours.

Yes. We regularly work inside a client's Git repositories, ticketing and change-management process, and can hand work over with documentation and pairing sessions.

LMS Advisor is an enterprise LMS built by our team. We include it in recommendations only when it fits your needs, and always disclose our relationship. Learn more.

Well-defined work is quoted at a fixed price. Larger or evolving work runs on a monthly retainer or a dedicated team. Try the cost calculator for an indicative range.

Yes. A 30-minute call to understand your goals and give you practical next steps - even if the answer is that you do not need us.

Yes. Send the site URL and the symptoms (slow pages, errors, a failed upgrade) through the audit form and we reply with the likely causes and a recommended fix.

Plugins and integrations typically take 1-4 weeks, migrations 4-12 weeks, and custom or enterprise builds several months delivered in phases with working software at each milestone.

Your current platform and version, hosting, number of learners, the problems you want solved and any must-have integrations. A requirements document helps but is not required - use the quote form.

Fixed-price projects are usually split into milestones. Retainers and dedicated teams are billed monthly. Exact terms are agreed in the written proposal.

No. We extend platforms through their supported plugin, hook and theme systems so your LMS stays upgradeable and secure.

SCORM 1.2 and 2004, xAPI (Tin Can) with an LRS, cmi5 and LTI 1.3 / LTI Advantage. Read our comparison of SCORM vs xAPI vs cmi5.

Yes - SAML 2.0 and OpenID Connect with identity providers such as Microsoft Entra ID, Okta and Google Workspace, including role and cohort mapping. See LMS SSO: SAML vs OIDC.

Usually, yes. We profile first (PHP, database, caching, cron, hosting) and then fix the real bottlenecks rather than guessing. See performance optimization.

Yes - separate branding, users and reporting per client organization, on Moodle, WordPress or a custom platform. Our guide to multi-tenant LMS architecture explains the options.

We build responsive, mobile-first learning experiences and can extend official apps such as the Moodle app, or deliver a custom app when offline learning or device features require it.

On your own servers, your cloud account (AWS, Azure, Google Cloud, DigitalOcean and others) in the region you choose, or a managed hosting partner. We can set up and manage the infrastructure if needed.

You do - including documentation and credentials.

Yes. We follow OWASP practices, work with least-privilege access, sign NDAs and complete security questionnaires. See LMS security.

We work on staging copies with anonymized data wherever possible, never store production data on personal devices, and follow your data-processing agreement.

We implement the technical controls - access control, encryption, audit logs, retention and consent - and document them for your compliance team. Compliance itself also depends on your processes and contracts.

Post-launch support for defects is agreed in every proposal. For ongoing peace of mind, a maintenance plan adds monitoring, agreed response times and emergency support.