Cakrawala Foundation
Shared direction · authorised access · cross-school reporting
A connected operating platform for schools
Bring academics, student records, people, finance, operations, school services, and many other modules into a platform that follows how schools work and grows with the foundation.
One foundation. Every school. One platform.
Synthetic sample data
The SatuSkola framework
This core language describes how SatuSkola is designed: adapting to supported needs, connecting context, and keeping school work manageable as institutions grow.
Supported custom fields, templates, formats, and settings can fit school needs.
Core records can be reused by related workspaces within relationships and permissions.
Product coverage spans learning, services, administration, and school operations.
Skola AI assists supported academic work with drafts that remain under user review.
The same platform can serve one or multiple schools with appropriate access scope.
Connected workspaces and context can reduce repeated entry and help teams focus on higher-value work.
Contextual workspaces help users reach important actions without navigating the entire platform.
From foundation to classroom
Leaders get an authorised view across schools. Each school keeps its own users, data scope, settings, and responsibilities.
Shared direction · authorised access · cross-school reporting
Its own curriculum and settings
Its own users and data scope
Its own operations and responsibilities
One ecosystem
The journeys below show how data can be reused without repeated entry. They represent only part of the relationships available across SatuSkola.
Portal and service access follow user relationships and permissions.
Assignments and school scope determine which classes are visible.
Journal posting follows the configured accounts and payment process.
Each user sees only permitted schools and actions.
My Classroom
Schedules, plans, assessment, and follow-up appear in teaching context—not as menus to hunt through one by one.
Complete does not have to mean complicated.See sessions, available plans, completed work, and sessions that still need preparation.
Review plans by day and ensure every session has the context it needs.
Read class assessment summaries and identify students who need follow-up.
Comfortable on every screen
SatuSkola reorganises its interface for laptops, tablets, and phones. Important information and actions remain readable rather than simply shrinking a desktop view.
Real application captures across four screen sizes and orientations
Summary, navigation, and lesson lists appear together so teachers can review the whole day.
Lesson cards flow vertically with comfortable touch space and intact task context.
Navigation and content redistribute the wider space without compressing important actions.
Sessions, planning status, and work needing preparation become easy-to-scan cards.
Skola AI
Skola AI uses the academic context already open, then produces a draft that remains subject to user review.
Less prompting. More context.
An adaptable operating platform
Every school has its own structure, data, roles, outputs, and governance. SatuSkola provides real configuration layers in supported areas rather than forcing every school into one rigid process.
Add institution-specific fields in supported areas including students, employees, planning, health, alumni, events, and home visits.
Combine workspaces, record ownership, actions, and school scope around organisational responsibility.
Supervisor approval can be required for deletion of supported record types; this is not a universal workflow engine.
Configure supported outputs such as report-card formats, planning templates, correspondence numbering, identity cards, and payslips.
Move data through supported formats and control who can view or manage each area.
Schools can retain their own users, settings, academic structures, and data scope.

Names, codes, languages, time zones, branding, documents, and baseline settings can follow each school unit.

Administrators can define labels, field types, order, required state, active state, and school scope.

Schools can decide when deletion of supported records requires supervisor approval. This is not a universal approval engine.
Configuration handles supported variations. When new needs emerge, SatuSkola’s modular structure allows additional capabilities to be developed without replacing the operating foundation already in place.
Roles and permissions
The roles below are common examples, not system limits. Administrators can combine access by workspace, record ownership, actions, and the schools within a user’s authority.
Practical governance
Data environments are separated between foundations. Within a foundation, school scope, roles, assignments, and permissions keep responsibilities clear.
Explore SatuSkola
See the main workspaces available in the platform, grouped around school work.
From curriculum structure to daily teacher work.
Student records from admission through family access.
Employee records, development, and compensation in one context.
Traceable student billing and accounting.
Daily school services share context with core records.
Activities, communication, and post-graduation relationships.
Control over schools, access, data, and outputs.
From curriculum structure to daily teacher work.
Student records from admission through family access.
Employee records, development, and compensation in one context.
Traceable student billing and accounting.
Daily school services share context with core records.
Activities, communication, and post-graduation relationships.
Control over schools, access, data, and outputs.
Built to grow
As students, users, records, modules, schools, and reporting needs grow, SatuSkola helps institutions preserve an organised operating model without rebuilding systems or adding unnecessary administrative burden.
Begin with the modules needed most, such as academics and student records, then add many other modules gradually.
Expand use across people, finance, services, administration, operations, and other school needs.
Add schools and users while preserving each school’s identity, settings, and data scope.
Investment shaped around your needs
We first understand the needs of your school or foundation. The investment discussion considers desired operating value, implementation readiness, and genuinely needed areas—not a forced package.
See the whole value
Disconnected spreadsheets, repeated entry, reports waiting to be assembled, and information dependent on one person all carry a cost. SatuSkola helps turn that burden into workflows that are connected, visible, and reusable.
The same information can serve connected work contexts, reducing repeated copying and reconstruction between departments.
Routine work becomes lighter, allowing time and capacity to move toward review, service, and higher-value decisions.
More centralised records reduce time spent waiting for files, combining spreadsheets, and manually assembling information.
Within their authority, leaders can review school information remotely, supervise faster, and rely less on verbal updates or paper records.
Investment perspective: SatuSkola’s value is not limited to the features used today; it also lies in lower administrative burden, better coordination, faster access to information, and the institution’s ability to grow while retaining clear control.
Begin with priority needs and add other modules when the institution is ready.
Approximate student numbers help determine an appropriate service scope.
School count, onboarding needs, data readiness, and operating complexity are considered.
Trial availability, special pricing, and full sponsorship follow consultation, implementation readiness, and applicable programme terms.
Discuss your school’s needs
Tell us about the situation, priorities, and plans of your school or foundation. We will help identify the most relevant modules and starting point.