← חזרה לעמוד הבית · Back to home

Folio · למוסדות אקדמיים
For academic institutions

Partnership reference · גרסה 1.0 · עודכן 7 במאי 2026

Folio הוא דשבורד סטודנטיאלי מקומי (Local-first) שמאחד Moodle, ידיעון ו־Microsoft 365 בחלון אחד. כל הנתונים נשארים על המכשיר של הסטודנט — שום דבר לא מועלה לשרת שלנו. השותפות עם מוסדות נבנית במדרגות, מהפשוטה לעמוקה. אתם בוחרים את הרמה.

Folio is a local-first student dashboard that unifies Moodle, the registration portal (Yedion / Aleph / etc.), and Microsoft 365 in one window. All data stays on the student's device — nothing is uploaded to our servers. Institutional partnership scales in tiers, from a handshake to embedded. You pick the level.

Availability note · Tiers 0 and 1 are operational today. Tiers 2 and higher are co-built per engagement on the timelines noted below — we don't pre-build per-uni adapters until a uni commits. תיאום זמינות: רמות 0 ו־1 זמינות כעת. רמות 2 ומעלה נבנות ביחד עם המוסד לפי לוח הזמנים שצויין.

5 רמות שיתוף פעולה · 5 cooperation tiers

Tier Status · סטטוס What we ask · מה אנחנו מבקשים What students get · מה הסטודנטים מקבלים System requirements · דרישות מערכת
0
Anonymous · אנונימי
Operational today
זמין כעת
Nothing · כלום. A polished tool. Folio uses the same Moodle Web Services + SAML SSO any official student-mobile-app uses. Folio רואה רק מה שהסטודנט רואה. Uni: 0 hours.
Folio: a per-uni profile entry. Already running.
1
Sanctioned · מאושר
Operational today
זמין כעת
Whitelist for Folio's User-Agent + 1-page acknowledgement letter ("Folio is a permitted client tool"). Optional iCal feed URL. Same features, lower error rate. Folio mentions "Sanctioned at [uni]" on its About page (PR for the institution, optional). First-line bug reports forwarded to your IT. Uni: ~3-5 hours admin/IT-policy time. No infra changes.
Folio: ~2 hours per-uni config.
2
Integrated · משולב
Co-build, ~2-3 weeks
בנייה משותפת, 2-3 שבועות
SAML SP registration in your IdP (1 hr identity team) · install our local_folio Moodle plugin or expose a registration-portal adapter · DPA template (drafted with Israeli counsel) signed under your existing data-protection framework · 90-day audit-log retention agreement. Real-time data, structured (not scraped). No second login — student signs in with the existing IdP click. Cohort-aggregate analytics for the institution (never per-student). 5-business-day bug-fix turnaround for your students. Uni: ~1 sprint (~80 hrs) — identity team + Moodle admin. Maintenance near-zero afterwards.
Folio: ~2 weeks dev — plugin + adapter + per-uni profile + audit-log mirror, built once you commit.
3
Partnership · שותפות
Available Q4 2026+
זמין מהרבעון הרביעי 2026
Read-only DB views or scoped API into the SIS · push-gateway for events · joint pilot cohort defined · NDA + DPA + MoU · audit access for your security team into Folio's logs. The full destination — every academic signal, real-time. Atlas (lecturer-side) features unlock. Class-cohort phase-3 features unlock. Anonymized aggregate analytics dashboard for chairs/registrar. Co-funded student licensing. Revenue share to the student council (10% of net). Uni: ~1.5-2 months — DB team + identity + security review + DPO + legal.
Folio: server-side relay (stateless), mTLS, pentest — built post-MISSION-16. We don't pitch this tier until that infra is operational and audited.
4
Embedded · משובץ
At invitation
בהזמנה
Inclusion in student onboarding · multi-year commitment · per-student licenses pre-paid by the institution (volume pricing) · joint roadmap input. Custom theme matching your brand · dedicated support tier (your IT calls our team direct) · contractual SLA · open-source the per-uni adapters under your copyright if requested. Uni: institutional contract level.
Folio: 1-2 employees by this stage. Quarterly security reviews. Reached when offered, not pursued.

What stays true at every tier · אינווריאנטים אדריכליים

  1. Student data sovereignty. Even at Tier 4, no Folio server stores per-student academic data. Local-first stays the rule. סוברניות נתוני הסטודנט נשמרת בכל הרמות.
  2. Opt-in for aggregate stats. Any cohort analytics require explicit student opt-in regardless of tier. הסכמה מפורשת לכל אגרגציה.
  3. Local encryption stays Folio-controlled. Tokens in OS Keychain (macOS) / DPAPI (Windows). Institution never holds the keys. הצפנה מקומית לעולם לא נחשפת.
  4. Adapter source available to institutions on request. The per-institution glue code is shared with your team so you can verify what runs against your infra. Repository access provided upon engagement. מחבר ה־Adapter זמין למוסד לעיון לפי בקשה.
  5. Audit log ownership at Tier 2+. When integrated with your SIEM, your copy is canonical. We mirror; you own. (Mirror code built per engagement, not pre-shipped.) הלוג הראשי הוא שלכם.
  6. Kill switch under 1 hour. You can revoke Folio's access at any tier in under an hour, with graceful student-side degradation to Tier 0. השבתה מהירה אפשרית בכל רמה.

Compliance posture · עמידה רגולטורית

What we'd ask in a first meeting · השאלות לפגישה הראשונה

  1. Which Moodle version are you on? (3.x vs 4.x — affects API path.)
  2. Which IdP runs your SAML SSO? (ADFS / Azure AD / Shibboleth / other)
  3. What's your registration portal — Yedion / Aleph / Bannerweb / in-house?
  4. Do you have a public iCal feed for academic calendar? Is it per-student authenticated?
  5. What's your data-protection officer's posture on local-first student tools? (Most are positive once they understand "nothing leaves the device.")
  6. Which tier feels right for a starting conversation? (We always recommend starting one tier above where you are now — never two.)

Contact · צרו קשר

דוד הרוני · מייסד ומפתח
partners@foliocampus.com
תגובה תוך 48 שעות · ללא התחייבות · ללא דמי ייעוץ.

David Haruni · founder & engineer
partners@foliocampus.com
Response within 48 hours · No commitment · No consulting fees.

Prefer a printable copy?