OpenEduCat

What OpenEduCat is

OpenEduCat is an open-source education platform, and No Code Studio is the part of it that lets non-technical staff build their own apps. The reader it is aimed at is an institution's IT team and the department staff who depend on it: student affairs, facilities, academics and similar offices that want a custom tool without a development project. Around the builder sits an education platform with a learning management system, a Student Information System, a timetable module, financial data, attendance and transcripts. The home page says "Join 3M+ users who run their institutions on OpenEduCat."

What you build and how

The company's description of who can build is plain: "If someone can build a moderately complex spreadsheet with conditional formatting and data validation, they can build an app in No Code Studio." The interface uses drag-and-drop for layout, dropdown menus for field types, visual condition builders for logic, and one-click publishing. The page says no programming, SQL, HTML or web development knowledge is needed. It recommends a four-hour training session for new builders and says that in the company's experience most staff produce their first usable app within one to two days of starting training.

The data layer is the platform itself. No Code Studio apps can read from and write to any data model in OpenEduCat, subject to the permissions IT configures. A student affairs app can pull student names and enrollment status directly from the Student Information System. A facilities app can reference room data from the timetable module. The page's point is that staff do not re-enter data the platform already holds, and that reports built on custom apps reflect real-time institutional data.

Governance is the center of the pitch, which is why this entry sits under internal tools. IT administrators set global policies that apply to all No Code Studio apps: which data models staff can connect to, which user roles can publish apps, whether apps require IT review before going live, and how long inactive apps remain before automatic archival. Every app runs inside the OpenEduCat platform with the same role-based access controls, audit trails, backup schedules and data retention policies as the standard modules. IT can also disable or archive any app at any time. The company's phrase for this is "governed self-service", and it says plainly "This is not shadow IT."

Maintenance after an upgrade is addressed directly. No Code Studio apps are stored as configuration data, not custom code, and when OpenEduCat upgrades these configurations migrate automatically in most cases. For major version upgrades the company's team runs a compatibility check on all custom apps before the upgrade proceeds. If an app needs adjustment, the changes are typically minor, such as updating a field reference or adjusting a view layout, and the page says the team has never seen an upgrade that required rebuilding an app from scratch. It also states there is no hard limit on the number of custom apps an institution can build.

The AI features sit beside the builder, not inside it. The AI Course Generator takes a topic, target level and semester length, and drafts a week-by-week outline with lecture topics, reading assignments, discussion prompts and assessment milestones. Lesson plans break each week into class sessions with warm-ups, core instruction, group activities and wrap-up assessments, following a backward design framework. The draft lands in the course editor, and nothing reaches students until faculty publishes it. Related tools on the same page include a quiz and assessment builder, an AI grading assistant that drafts rubric-aligned feedback while teachers assign every grade, a student support tool that answers questions from institution-uploaded course documents with citations, and content recommendations drawn from a faculty-chosen pool. For models, the page describes a bring-your-own-model route: a request goes from your OpenEduCat instance to the endpoint you choose "under your own agreement, region, and data terms", with guardrails, spending budgets and audit logs applied to every generation.

Beyond apps, the pages mention attendance from LMS sessions syncing with the attendance module, quiz grades flowing to student transcripts, online fee collection, and integration with "your existing student systems, payment platforms, communication tools, and campus infrastructure."

Evidence from the pages

On licensing, the home page says "LGPL-3.0 licensed" and that the Free Edition is "genuinely open source", inspectable, modifiable and redistributable under an OSI license, "not a marketing label". The cloud page offers a choice between cloud and self-hosted deployment on the same platform with the same features, and says you can start with cloud and migrate to self-hosted later, or the other way round.

The cloud page sets out the two models. Cloud-hosted: setup time in minutes, server management handled by OpenEduCat, automatic updates, a monthly subscription cost model, a choice of data hosting region and automatic scaling. Self-hosted: setup time in days to weeks, your IT team manages the servers, manual updates, a one-time license plus ongoing maintenance costs, data staying on your servers and unlimited code-level customization. The hosting regions listed are US, EU, Asia and the Middle East. The page states FERPA compliance for US institutions and GDPR compliance for EU institutions, plus encryption in transit (TLS 1.3) and at rest (AES-256). It says OpenEduCat's mobile app supports offline content access for students, with progress syncing once connectivity returns.

On price, the home page promises "Fixed pricing that doesn't penalize you for growing enrollment. No per-student fees. No surprise invoices." It publishes no amounts and offers a button to "Configure my institution's pricing". The AI page mentions a free trial of 15 days with no credit card. A reviewer quoted on the home page says "The product is nicely priced, and the support is exceptional." That is a testimonial the company chose to display. The pages publish no limit on apps, and no template count or integration count for No Code Studio.

Who it suits and who it does not

No Code Studio suits a school or university that already runs, or plans to run, OpenEduCat and wants departments to build small tools on top of the student, course and timetable data without raising a development ticket each time. IT keeps the controls: which data models are reachable, who can publish, whether review is required. Teams that want to inspect or modify the source, or to host on their own servers, have the LGPL-3.0 Free Edition and a self-hosted option to start from.

It is not a general-purpose app builder. The builder lives inside the education platform and reads that platform's data models, so a company with no OpenEduCat deployment has nothing to point it at. The pages describe apps that run inside OpenEduCat for staff, and say nothing about publishing them as public sites or customer-facing products. They do not mention exporting an app as code, and they show no integration counts. A buyer who needs HIPAA or a certification beyond FERPA and GDPR should ask, because the pages do not name one.