Inside the platform
How Simetri works, one module at a time
Simetri is the work platform for the teams behind a family of brands. This page walks through each part of it in turn, what it does, why it was built that way, and which pieces are live today and which are still being built.
A map before the tour
Before we open any single screen, it helps to know where everything lives. Simetri is spread across three homes, each built for a different part of working life.
The first home is Simetri, the team app, at team.simetri.work. This is where people spend their working day: they talk in chat, clock in and out, ask for leave, keep their own notes and to-dos, and receive their payslips. Most people open it from the home screen of their phone, the same way they would open any other app.
The second home is Simetri Sanctuary, the HR console, at sanctuary.simetri.work. It sits behind sign-in and belongs to the people who look after the team as a whole. Staff records, contracts, approvals for leave and overtime, the leave calendar, access to other apps, and recruitment all live here.
The third home is payroll, which runs in a separate finance system. Salary figures stay there, and a payslip travels to Simetri only when a person decides it should.
All three homes are live today, and they are used by the teams of the brands in the group. Seven brands currently hire through Simetri: Eduprima, Akselera, Kaskadia, Simetri, Konstelar, Neksus and Eduspine. Their work ranges from education and private tutoring to corporate training, creative services, technology, and the group's shared systems. The teams are based in Indonesia, so the platform keeps its operational time in WIB.
With that map in mind, let us walk in through the front door, which for most people is chat.
Chat, where the working day is spoken
Chat is the part of Simetri people open most often, so it was built to feel familiar and to stay out of the way. There are group conversations for teams and topics, and there are direct messages between two people. Attachments travel with messages, a message can be forwarded to another conversation, and any message can be turned into a link with a single action.
That last feature deserves a closer look, because it shows how the platform thinks about privacy. When you copy a link to a message and paste it somewhere else, the link opens only for people who are members of that conversation. Someone outside the group who clicks it sees a polite page saying the conversation is closed to them, and nothing from inside the conversation is shown. So a link can be shared freely as a pointer, while the content it points to stays exactly where it belongs.
This matters in a workplace where people move between many groups in a single afternoon. A finance thread, a hiring thread and a project thread can all be referenced from one place without anyone worrying about who might accidentally read what. The rule is simple and the system enforces it on its own, so nobody has to remember it.
Chat is also deliberately calm. You will find no heart symbol in any of the office apps, since this is a place of work, and the visual language stays plain and warm. When an assistant helps someone write on another person's behalf, the message carries a mark that says so, and a reader always knows how a message came to be. The goal is a conversation space that people trust, where what you see is what was said, by whom, and in which room.
Machine reports in the same rooms as people
Every group of teams relies on tools that report on themselves: systems that finish a nightly job, notice something unusual, or prepare a summary each morning. In many workplaces those reports land in a separate inbox, a different app, or a dashboard that someone has to remember to open. Simetri brings them into chat.
When one of the group's tools has something to say, its report arrives in the chat group of the team that cares about it. The finance team sees finance reports in its own room, the people who look after the websites see their reports in theirs, and so on. The report sits in the same stream as the human conversation around it, which means the discussion about a report can happen right underneath it.
The reasoning here is about attention. People already live in chat during the working day. Asking them to check one more place adds a small cost every single day, and small daily costs are exactly the ones that get skipped. When reports land where people already are, they get read, and when they get read, problems are noticed while they are still small.
Because team conversation and automated reports share one place, the history of a decision also stays whole. Someone joining a team later can scroll back and see the report that raised a question, the conversation that followed, and the decision that closed it, all in order. Nothing has to be reassembled from three different tools.
Assistants that help and name the decider
Some chat groups have an AI assistant attached. Every assistant belongs to one team and exists to help it. It can offer support when a question comes up, draft a reply or a summary, and answer the kind of question that has a clear answer.
What an assistant never does is take a decision away from the person who owns it. When a matter needs someone's judgement, the assistant says so and names the person who decides. It might draft the message, gather what is known, and point out what is missing, and then it hands the matter to the right human by name. The assistant's role is to make that person's work lighter while the decision stays in their hands.
This design choice comes from a plain observation about teams. When a tool quietly makes decisions, people stop knowing who is responsible, and trust drains away slowly. When a tool prepares the ground and then clearly hands over, people move faster and still know exactly who said yes. Responsibility stays visible.
Assistants are also honest about authorship. If someone lets an assistant compose a message for them, a visible label tells the room how the words came about. A reader can always tell the difference between a person's own words and words drafted with help.
The same principle runs through the rest of Simetri, especially in recruitment, which we will come to later. The machine prepares drafts, analysis and proposals, the final call belongs to people, and a proposal only takes effect once a person confirms it, and that pattern repeats wherever an assistant appears.
Attendance and the working day
Attendance is the part of Simetri that records the shape of each working day. It starts with clock in and clock out. A person opens the app at the start of the day, clocks in, and clocks out when they finish. The record is theirs to see, and it becomes the shared basis for everything that depends on time: leave balances, overtime, and the conversations HR needs to have about a month.
A deliberate choice sits underneath this module: attendance happens only in Simetri. Other apps in the group may know who a person is through their Simetri account, yet none of them records attendance. There is one place to clock in, one record of the day, and one set of rules applied to it.
The reason is trust in the numbers. When attendance can be recorded in several places, the records drift apart, and someone eventually has to sit down and reconcile them by hand. Mistakes in attendance turn into mistakes in pay, which are the most painful kind. A single home for attendance removes the reconciliation step entirely.
Sometimes a person cannot clock in themselves, for example because they were somewhere without access or their phone failed them. For those moments, HR can record attendance on their behalf from Sanctuary. The record still lives in the same place, with the same rules, and it is clear that it was entered on someone's behalf. The exception is handled inside the system, so the single source of truth survives the messy reality of real days.
Leave, overtime, late arrival and early leave
Around the basic clock sit the requests that make a working life flexible. All of them start in the team app and are approved in Sanctuary by the HR person on duty.
Leave is requested from the phone. A person picks the dates, adds what is needed, and sends it. The team app also shows who is away, so colleagues can plan around an absence without having to ask around. Once approved, the leave appears on the leave calendar in Sanctuary.
Overtime is logged on a short form. A person writes down the overtime they worked and submits it, and it goes to HR for approval. The form is kept brief on purpose, because a long form at the end of a long day is a form that gets skipped or filled in carelessly.
Late arrival and early leave have their own requests. When someone knows they will arrive late or needs to leave early, they can say so through the app before it happens, which turns an awkward conversation into a simple, recorded request.
The thread that ties these together is that everyone knows where to go. A person who needs time off, or who worked late, does not have to remember which form lives where or who to message. They open the same app they use all day, make the request, and see its status. On the other side, the HR person on duty sees the requests arrive in one console and can approve them in one place.
That shared route also means requests are never lost in a private message. Each one is recorded, each one has an owner, and each one has an answer the requester can see.
WorkDesk, a room that belongs to one person
WorkDesk is where a person keeps their own work organised. It holds personal to-dos, notes, a calendar, private documents and daily reports. People use it to plan their week, keep track of what they promised, write down thoughts before a meeting, and keep a record of their own days.
The most important thing about WorkDesk is who can read it. A person's WorkDesk is readable only by that person. HR cannot open it. Leadership cannot open it. The platform was built so that there is simply no door into someone else's WorkDesk, and that is a choice the system holds firmly.
Why would a workplace tool protect a space from the workplace itself? Because people only write honestly in a place they trust. A to-do list that a manager can read becomes a performance. A note that HR can open becomes careful and vague. When a person knows their WorkDesk is theirs alone, they can use it the way a good notebook is meant to be used: messy, candid and useful.
This privacy also connects to a wider principle in Simetri. The group wants to measure work fairly, and the recruitment design says plainly that measurement covers work only. WorkDesk and payslips stay private. What gets assessed is the work a person shares and delivers, through the channels meant for it, and their private planning stays their own.
So WorkDesk sits inside the team app, a few taps from chat and attendance, yet it behaves like a locked drawer in a shared office. Everyone has one, and every key fits only its owner's lock.
Finance and the quiet payslip
The Finance module in the team app holds payslips. When a payslip for a period is ready, it appears here, and the person can open it, read it, and keep it.
Each slip opens for one reader, the person it belongs to. Just as with WorkDesk, HR and leadership cannot open someone else's payslip inside Simetri. Each person sees their own pay, privately.
The notifications follow the same care. When a new payslip arrives, the person gets a notification that a slip is ready. That notification never contains an amount. The number appears only once the person opens the app and looks at the slip themselves.
This small detail solves a real problem. Phone notifications appear on lock screens, on shared tablets, on a screen held up during a video call, or on a phone lying on a table where others can see it. A notification that showed a salary figure would leak the most private number in a person's working life to whoever happened to glance at the screen. By keeping amounts out of notifications entirely, Simetri makes sure the only person who sees the number is the person who chose to open it.
It is worth saying where the numbers come from, because this shapes the design. Salary figures are kept in payroll, in a separate finance system. Simetri receives a payslip only after it has been published there. The team app is the place where a slip is delivered and read, and the calculation stays in the system built for it. We will look at that handover more closely when we reach payroll.
Me, the home screen, and the right language
The last module in the team app is Me, which holds a person's own profile. It is where someone sees how they appear to their colleagues and keeps their own details in order.
Around all these modules sits a set of choices about how the app reaches people. Simetri is an installed web app. A person adds it to the home screen of their phone, and from then on it opens like any other app, full screen and ready. The newest version is simply there the next time it opens, ready without a store download or a manual update.
Push notifications come with it. When a new message arrives, a request is approved, or a payslip is ready, the phone can tell the person, even when the app is closed. This is what lets chat work as the centre of the day, because people can step away from the screen and still know when something needs them.
Language is handled with the same care. The app is in English by default, with Indonesian alongside, so each person can work in the language that feels most natural to them.
Together, these choices make Simetri feel close at hand. It lives on the phone people already carry, speaks a language they are comfortable in, and quietly tells them when something has changed.
Sanctuary, the console for the people who look after people
If the team app is where each person manages their own day, Sanctuary is where HR looks after the team as a whole. It sits at sanctuary.simetri.work, behind sign-in, and it is built for the people whose job is to keep records straight, approve requests and bring new people in.
Here is what lives in Sanctuary:
- Staff records, the shared, accurate picture of who works in the group and in which team.
- Contracts, kept alongside each person's record.
- Approvals for leave and overtime, handled by the HR person on duty.
- Attendance on behalf of a person, for the days when someone could not clock in themselves.
- The leave calendar, which shows at a glance who is away and when.
- App access, where people are given the right level of access to the group's other staff apps.
- Recruitment, with openings, applicants, and the path each opening uses.
The split between the team app and Sanctuary follows a simple idea: each person should see the tools for the work they actually do. A team member does not need a console full of other people's records, and HR should not have to dig through a personal app to find an approval queue. Separating the two keeps each one clear.
The split also protects privacy in a concrete way. Sanctuary holds the records HR genuinely needs. The private rooms of the team app, WorkDesk and payslips, stay outside it. HR can approve a person's leave and keep their contract up to date without ever being able to read their notes or their pay. The console is powerful exactly where it should be, and nowhere else.
One account, many doors
A Simetri account opens the team app, and it is also the key to the group's other staff apps. When someone joins, they get one account, and from that account they can be given access to whatever other tools their work needs.
Access is granted per app. Each app is its own decision, made on purpose for each person. That access is granted either by leadership or by a manager appointed for that particular app, who knows what the app is for and who should use it.
Some roles carry more weight than others. Sensitive roles, such as owner, admin, or full access, are granted only by the founder. An appointed manager can give people the everyday access they need, and the roles that could change or reach into everything stay with one person who is accountable for them.
Trainees are handled with particular care. A trainee can be given access with an end date, and when that date arrives the access expires on its own. Nobody has to remember to remove it, and nobody's access lingers after a training period has ended.
The reasoning behind all of this is about fewer manual steps and fewer forgotten loose ends. In many workplaces, every app has its own list of users, and when someone joins, moves or leaves, a person has to update each list by hand. Lists drift, old accounts stay open, and nobody is quite sure who can see what. With one account as the key, there is a single place to look. With per-app access, each door is still a conscious choice. With expiry dates for trainees, the most commonly forgotten clean-up takes care of itself.
Careers pages and how an opening begins
Recruitment is the newest part of Simetri, live since 26 October 2026, with more stages being built. It begins with its public careers pages.
There is a careers page for every brand in the group, and every opening carries two labels, its brand and its city, letting a candidate know at a glance who the team is and where it works. Each opening can be shared with a link made for a particular channel, so the team can tell which channels bring good applicants.
Every opening follows the same route. It is requested by a team head, approved before it is published, and it declares its criteria up front. That order matters. The criteria are fixed before the first applicant arrives and locked once applications open. Nobody can quietly move the goalposts halfway through, and every applicant is measured against the same description.
Openings are tagged with the team they belong to. There are 14 teams in that list today, from Education Consultant and Education Management to Tech, Marketing Web, Production, Finance, Human Resources and Corporate Training. There are also 12 role templates ready to start from, among them Full Stack Developer, Customer Service, Video Editor, Content Creator and General Affair, so a team head is rarely starting from a blank page.
The design reason is fairness from the very first step. When criteria are written and approved before anyone applies, the opening becomes a promise. Candidates can read exactly what the role asks for, and the people reviewing them have a fixed reference to work from.
You can browse current openings on our careers page.
Declared requirements and the one-screen form
Some roles have a genuine hard requirement. A role might need a driving licence, the ability to work daily at a given office, a particular start date, or in a specific job an age range. Simetri lets an opening declare these, with careful limits.
An opening may declare at most 3 hard requirements. Each one must be job-related, written with a reason, and approved. The system then checks each requirement as a simple yes or no, equally for every applicant. An applicant who answers no to a declared requirement sees the application end on the spot, with a courteous note naming the requirement in question. They learn straight away, and nobody waits weeks for an answer that was clear from the start.
Just as important is what the rule forbids. An undeclared preference has no power to remove anyone. If it was not written down, reasoned and approved, it plays no part.
Everything fits on a single screen, which asks for:
- full name, email, WhatsApp number and city;
- a CV file (PDF or Word, 4 MB at most), or a link to a CV;
- where the person heard about the opening;
- one optional short note;
- consent.
Then it adds one question for each declared requirement, and only when the opening declared it. The form asks for no photo. An age question appears only when an age requirement was declared for that job.
The reason for keeping it this short is respect for the applicant's time. A long form at the front of a hiring process mostly measures patience. Simetri asks for what is needed to begin, and leaves the longer questions for later, in conversation, once there is a real reason to ask them.
After applying: careful files and a private page
Once someone presses submit, a few quiet protections take over. CV files are checked from their bytes, from what is actually inside the file, so the content decides what the file is. A file pretending to be a PDF is recognised for what it is. Anti-spam protections and rate limits guard the form, so the team's attention goes to real applicants.
Each applicant then gets a private page of their own. It shows their status in plain words, so they always know where things stand. From that page they can withdraw their application, or ask for their data to be erased. Both are choices the applicant can make directly, without having to write in and hope someone notices.
The privacy rules for applicants were designed around Indonesia's law on personal data protection, and an applicant's details get the protection a colleague's would. The design sets out these commitments:
- Every opening of a CV is logged, so there is a record of who looked at it.
- Applicants who were declined or withdrew, and who never opted into the talent pool, lose their CV and documents from our records 90 days after the opening has closed.
- The talent pool is optional, and when someone does join it, it lasts 24 months from their consent.
- Erasure requests are handled within 7 days.
Beneath these sits the most important commitment of all. A person makes every decision. AI never declines an applicant, and AI never hires one.
The thinking here is simple. Applying for a job means handing over personal information to strangers, often at an anxious moment. Applicants deserve to know what happens to it, to see their own status, and to be able to leave cleanly. Building those controls into the applicant's own page puts that power in their hands.
A path for every opening
Between application and decision lies the path, and in Simetri each opening has its own. The steps are chosen from a library: screen, task, phone call, interview, role play, trial day, reference check and training. A team picks the steps that suit the work.
The examples show how different those paths can be. A sales or consulting role might go screen, role play, interview, training, because talking with people is the heart of the job and a role play shows it best. A tech or creative role might go screen, task, interview, because a real piece of work tells you more than any conversation. A general affairs role might go screen, phone call, trial day, because seeing someone in a real working day is the clearest evidence.
That idea runs through the whole design: the closer a step gets to the actual job, the more its evidence weighs. A CV is light evidence. A short task is heavier. An interview and a role play are heavier still, then measured training, then months of real work. Each path climbs that ladder in the order that fits its role.
Real hiring is never perfectly tidy, so HR has two adjustments for a single applicant. They can fast-track one applicant past a step, for example when someone has already shown that skill in a clear way. They can also add a step for one applicant when something needs a closer look. Each of these moves needs a written reason, and that reason is kept. Every judgement is written down, so anyone looking back can understand why one applicant's path differed from another's.
Applicant codes, waiting clocks and an AI recruiter
A few more pieces keep recruitment fair and moving.
When a new applicant arrives, the recruiting team is told through chat, and the announcement uses an applicant code, never the person's name. There is also a morning digest that gathers the new applicants together. Using a code keeps the first moment of attention on the application itself. It is a small, practical expression of a larger principle in the design: merit first, identity later.
Each stage of the path shows how long the applicant has been waiting for us. When the wait runs long, a reminder goes out. Every stage has an owner, and the clock is visible, so nobody waits silently. An applicant who is stuck becomes something the team can see, and anything the team can see, it can fix.
Writing a new opening is helped by an AI recruiter. Give it a short request and it returns a draft with a title, the wording of the public post, criteria, a proposed path, and each requirement paired with its reason. Someone on the team goes through the draft, edits what needs editing, and approves it. People direct the recruiter in conversation and carry out the work themselves, and nothing it proposes moves until a person agrees.
For now, the team contacts applicants with WhatsApp links, while email to applicants stays off. If you have a question about an application, your private applicant page and the contact page show where to ask.
What is being built next
Everything described so far is live. The recruitment design goes further, and these next pieces are being built now:
- A single applicant database shared across the group, which will import past applicants too. An applicant who narrowly missed one role can then be contacted first when that role opens again.
- Blind screening views, where reviewers judge skill with identifying details such as name, photo and age kept out of view, apart from a declared, job-related, approved requirement.
- Structured scorecards that interviewers fill in independently, so each judgement is their own and is written down.
- Interview slots that applicants pick themselves, which saves the back and forth of scheduling.
- A measured training stage between acceptance and employment.
- Offers that read salary bands from payroll, so the figures stay in the system that owns them.
- Onboarding checklists for a new person's first days.
- AI summaries and suggested ordering, read from blind fields only.
- Fairness analytics, which will compute pass rates per assessor and show outliers with numbers.
That last item reflects a principle worth spelling out. Bias is measured and never accused. When the analytics arrive, they will show patterns with numbers, so a conversation about fairness can begin from evidence. The aim is a clear picture that helps everyone improve.
The longer arc is one continuous loop of sorting, training, testing and evaluating that begins with an application and keeps turning while someone works here. Good performance is recognised in the open, and anyone having a hard time is given a written goal, help, and time before leaving is ever on the table. Each person can see the criteria and numbers that apply to them, coaching is offered ahead of any consequence, and data can be used to appeal any judgement. The About page explains the thinking behind each of these promises.
The reasons underneath it all
Having walked through every module, you can see a handful of ideas returning again and again. They are the real design of Simetri, and the screens are how those ideas show up.
Privacy belongs to the person. WorkDesk is readable only by its owner. Payslips are readable only by their owner, and their notifications carry no amount. Chat links open only for members. Applicants can withdraw or ask to be erased from their own page. Each answer to the question of who should see something is built into the system, so it holds without anyone having to remember it.
Fewer manual steps. One home for attendance means no reconciling. Machine reports land in chat, where people already are. One account opens many apps, and trainee access expires on its own. Each removed step is one less chance for something to be forgotten.
Nobody waits. Requests show their status. A declared requirement that is not met closes an application at once, kindly, with the reason named. Recruitment stages carry waiting clocks pointed at the team. The platform treats someone's time as worth protecting, whether they are a colleague or a stranger applying for their first role with us.
People decide. Assistants name the decider. The AI recruiter drafts and a person confirms. A human presses Publish on every payslip. AI never declines and never hires.
These ideas come from a simple wish that has guided the whole platform: a workplace that is meritocratic and also humane, with less friction at the front and real certainty about who does good work. The name Simetri means symmetry, and its mark is two identical corners turned to face each other, one in Clay and one in Ink. In balance, in motion.
If you would like to know more about the group behind it, read about Simetri, or return to the home page.
Work with the teams behind our brands
Openings from every brand live on one careers page, and applying takes a single screen.
Social, a timeline written by people
Next to chat sits Social, a team timeline. If chat is where work gets done, Social is where people share the moments around the work: a team finishing something they are proud of, a new face joining, a small celebration, a photo from a day out.
Social is written by people. That is a firm rule of the platform, and it shapes how the timeline feels. When you scroll through it, everything you read was posted by a colleague who wanted to share it, so the space stays quiet, personal and easy to read.
The single exception is birthdays. On a person's birthday, Simetri posts a greeting, and each greeting is a card drawn from that person's world of work. Someone who spends their days with learners might receive a card that reflects that world, and someone who works with code or cameras might receive one that reflects theirs. The card celebrates the person through the work they do, which keeps it warm and personal while staying appropriate for a workplace.
Why keep machines out of Social? Because a timeline loses its meaning the moment people suspect it is being filled for them. A space that is clearly human invites people to post, react and look forward to it. Keeping it that way costs nothing, and it protects one of the few places in a work app where colleagues simply see each other as people.