Mathias Celis, PhD

@daylightco well, that didn't happen...

To the wonderful ecosystem of Daylight users, We have an update on Sol:OS and our software timelines. We want to bring you in on our priorities and how we're thinking about things as we learn and grow. The software team at Daylight has reached a milestone in stability and capability to better plan out into the future, and we want to provide an update on what we’re working on. Our software team is currently focused on building strong foundational systems for the product. For example: a better system for device updates, a new system for performant reading, marking, and editing documents, and groundwork towards our operating system. We're prioritizing these projects to make sure we have a solid foundation to deliver the experience of computing, reading, writing, and using apps that we envision is possible. Unfortunately, we need to walk back a promise we made. We originally stated that we’d ship a version of Sol:OS at the beginning of this year. We didn’t properly anticipate the level of rebuilding that we needed to create the kind of operating system we’re proud of. Between paying down tech debt and coordinating among software, hardware, and our manufacturers, our estimates were off. In March, we hit pause and took stock of each surface we were building. Now, with a more complete picture, we have a better sense of where we are and what happens next. A lot of our current work will initially be less visible to users. There has been a lot of internal deliberation and we recognize this tradeoff. We’re focusing our energy here to invest in the reliability and long term future of Daylight. Building the foundations is going to take us some time, and we’ll balance shipping small wins for our users with larger chunks of work. We now expect to launch the foundations of a Daylight operating system closer to Q4 this year. You can expect regular updates from our team like this one every couple of months starting this summer. We are truly excited to show you what we're creating. It's just going to take a bit more time than we expected. We welcome any questions and aim to give you all the information we know now. We’re working to deliver a future of computing that we’re proud of. With warmth, Tanuj, Ethan, the rest of the software team, and the whole Daylight organization

@daylightco Yes please! Sign me up! :)

AI demos all try too hard to be fancy and impressive We wanna just focus on it being the most seamless, simple, & friction free It turns out it helps to have both the OS and hardware to pull off super buttery smooth AI UX We don’t even call it AI We just call it mAgic Ink Only on daylight. Comment below if you want to beta test.

@daylightco Any updates on Sol:os v1 release timeline?

@damienghader @Lovable Cheat sheet

FCK it. Here's all the sauce. After shipping 100+ apps with @Lovable — I made the ULTIMATE Design Cheat Sheet. Every prompt. Every design system pattern. Every cloud config + infra setup. Every component standard + best practice we actually use to achieve world-class UI. All in one doc. Follow + comment "Cheat Sheet" and I'll DM it to you.

@damienghader @hiyaitsciaran @Lovable Cheat sheet

@hiyaitsciaran @Lovable Yes everyone who responded within the first week, I was running an automation.

@MarketbyJesse @AlkmistHQ Not really geared towards devs. More so towards teams managing complex collaborations, like auditors, accountants, legal, M&A... where multiple clients, entities, and deadlines collide. They often don't have the resources to manage this efficiently in a way that's GDPR compliant

@mathiascelis @AlkmistHQ If I'm correct, you're implying your tool solves unplanned chaos, something of that nature. Maybe the dev can't figure this out or that out, your tool makes it easier for them to thrive or work ??

One platform. Every stakeholder. Zero chaos. Audit engagements have more parties, more deadlines, and more moving parts than ever. Email wasn’t built for that. Spreadsheets weren’t built for that. But @AlkmistHQ is. #ClientExperience #Alkmist #SOTA25

@MarketbyJesse @AlkmistHQ @MarketbyJesse so essentially we solve this with great dashboarding, epic ux.

@mathiascelis @AlkmistHQ Still confused on what alkemist is all about

@MarketbyJesse @AlkmistHQ When you work together with consultants like @Deloitte , @KPMG you often have multiple services and projects going. All of this is coördinated through email and excel. Nobody has an overview of where the project is, what you need to do and what the upcoming important dates are.

Alkmist Secures €1.8 Million Funding Round #SaaS #AI #Legal #Audit #CollaborationPlatform #Documents & #Communication #AuditCollaborationTools #Funding #Alkmist thesaasnews.com/news/alkmist-s…

Alkmist raises €1.8M to streamline collaboration in complex processes tech.eu/2025/09/09/alk…

Alkmist raises €1.8M to streamline collaboration in complex processes ift.tt/uIP89bN

Gentse start-up Alkmist haalt 1,8 miljoen op om audits te stroomlijnen #Echobox=1757391246" target="_blank" rel="nofollow noopener">tijd.be/ondernemen/waw…

New Raise 🏛️ Company: Alkmist 🔗 Website: alkmist.com 📊 Amount: €1.8 Million 🔄 Round: Seed 🧮 Valuation: N/A ⚙️ Industry: Software & SaaS

Chaos is a choice. So is @Alkmisthq #AuditTech #FutureOfWork

When your audit team suddenly stops complaining about client chasing… Yeah, there’s a reason. 👀

🧪 Peer-reviewed in Int. Journal of Environmental Research & Public Health 📄 doi.org/10.3390/ijerph… 📰 Summary in Belgian press: bit.ly/nieuwsblad-stu… #nudging #behavioralscience #standingdesk #futureofwork #HRtech #workplacehealth #defaultdesign #fieldstudy

✅ Want results? Try this: - Introduce a “high desk policy” - Default desks to standing height - Be transparent about the why - Normalize it visually (posters, peers, prompts) Tiny frictions. Massive impact.

🚨 New publication alert! Our study with @wduyck and @NicolasDirix at @ugent & @securex just got published in @IJERPH_MDPI : ➡️ A tiny change at work led to a 922% increase in standing. No mandate. Just a smarter default. 👇 Here’s what we did, and why it worked so well: