Software company · Johannesburg, ZA

Existence

You’ll never be here again.

We build e_core, the Flutter framework behind our six live apps, and we build apps for teams who’d rather ship in weeks than months.

Talk to sales See the apps

30sfrom zero to a running app

4×faster to MVP

15modular packages · 7 layers

6+of our own apps live on it

Programmes and Partners

The framework

The boilerplate is already solved.

All of e_core →

One command scaffolds a complete Flutter app, production-ready and fully customisable. Your team starts at the part that makes your product unique.

$ e_core create my_app
Creating new e_core app…
✓ Auth system configured
✓ Settings screens generated
✓ Theme system initialized
✓ Routes configured
✓ Providers set up
Done in 28.4s. Run cd my_app && flutter run

Complete auth, settings and profile screens, theme dialogs, guarded routing, provider setup, from one command.

OUT OF THE BOX

Authentication

Email, phone, and social sign-in, Google, Apple, Microsoft, with complete verification flows.

ANY BACKEND

Backend-agnostic

Switch between Firebase, REST, Supabase, or GraphQL without rewriting app logic.

15 PACKAGES · 7 LAYERS

Modular architecture

Independent packages with clean separation, use only what you need; tree-shaking removes the rest.

12+ LANGUAGES

Internationalisation

12+ languages out of the box, with RTL support for Arabic, Hebrew, and Farsi.

TYPE-SAFE

Smart routing & state

Auto-configured routes with role and premium guards; centralised, testable Riverpod state.

90%+ COVERAGE TARGET

Built for testing

Easy-to-mock providers; unit, widget, and integration tests with Firebase emulator support.

Total cost of ownership

The code you will never maintain.

Every app carries a second codebase that is not the product: auth that must survive provider changes, screens that must survive OS releases, SDKs that deprecate on someone else’s schedule. On e_core that surface is ours. We patch it, upgrade it, and run it across six production apps of our own before it reaches yours.

SurfaceBreaks whenMaintained by

Auth and verification flowsproviders change APIs, platforms change privacy rulesExistence, under SLA

Settings and profile screensevery OS release, for the life of the productExistence, under SLA

Theme systemMaterial revisions, new form factorsExistence, under SLA

Routing and access guardsauth, role and premium logic driftsExistence, under SLA

Datasource layerbackend APIs move, Firebase, REST, Supabase, GraphQLExistence, under SLA

Localisation, 12+ languagesnew markets, RTL edge casesExistence, under SLA

Your product codewhen your roadmap says soYours. That is the point.

AI writes code faster. Someone still has to integrate, harden, and maintain it. That is the part we sell.

Ask us for access →

AI-native engineering

How we build.

We’re a deliberately small team that ships like a large one. Not by typing faster, by engineering the process itself: every ticket runs through an AI agent pipeline we designed, constrained, and supervise.

The pipeline · every ticket

01Plan

02Adversarial review

03Test-driven implementation

04Eight-lens review

05Commit

Loops until pass · hard iteration capsHigh-risk work adds human gatesEvery plan · verdict · result on the ticket

HarnessPlaybooks, not prompting.Agents follow written playbooks for planning, review, and implementation, versioned in the codebase, next to the code they govern. The pipeline is the same every time.

Risk tiersAutonomy, earned by risk.Routine tickets run end-to-end on their own. Security, payments, migrations: anything hard to undo adds mandatory human gates, and every finding must cite the decision record it rests on. “No guidance found” is an accepted answer. Inventing one is not.

ReviewReview that argues back.Before any code, a devil’s-advocate agent attacks the plan against our architecture rules. After, eight expert lenses review the result, architecture through error handling. Tests come first throughout, with 90%+ coverage enforced on business logic.

QAQA that taps the screen.A QA agent boots the app on a device emulator and tests it tap-by-tap, on video, against every acceptance criterion, then writes regression tests only for what it actually saw pass. Failures are reported, not papered over.

Humans own the judgment.People decide what gets built, adjudicate every gate, and nothing ships without one of us. You get faster delivery with nothing sacrificed, and a full, auditable trail of how your product was built.

The craft didn’t leave. It moved up a level.

The team

The people at existence.

All build what it ships.

The whole company fits in one room. The work does not.

Chief executive officer · FounderSiyabonga KubekaFounder.Direction and final calls.

Chief technology officerMushagi MayiboCode, e_core and releases.Joined 2026

Chief operating officerLebohang MashigoDelivery, operations, people.

Chief sales officerKhumo LetlapeRevenue, licensing, partnerships.

The build unit3 engineers

Morena RamailiEngineer

Tshepo MohaleEngineer

LehlogonoloEngineer · BA

One unit, one pipeline. They plan, review and build together.

Working with us

Build on it, or have us build on it with you.

Enterprise SLA

Your team ships on e_core. We stand behind it.

· All 15 packages, source access

· Unlimited developers

· 24/7 priority support

· Private Slack channel

· Architecture review

· Custom feature development

· Migration assistance

· Training sessions

Contact sales

Accelerated delivery

We deliver your app on e_core, at framework speed.

For teams that want the outcome, not the codebase: the people who built the framework, and ship 6+ production apps on it, build yours. Production-grade from day one, because the core already is. Handover, or ongoing under SLA.

See how the framework works in the docs, then bring us in when the stakes rise.

Scope a build

The proving ground

We run our own apps on the core we sell.

All apps →App Store ↗Play Store ↗

Six-plus products live on Android, iOS, and web, through real App Store review, in front of real users, monetising. Every release hardens the framework before it reaches your team. And each one exists for a reason: technology in service of a fuller, more present life.

Every one of them is why the framework holds. You’ll never be here again.

From the team

Notes from production.

All posts →

How we spec a build

EngineeringOne click to context: writing requirements so nobody has to askThe most expensive question in software is "what does this actually mean?" Here is the rule that stopped our engineers ever having to ask it: the ticket carries the headline, one linked page carries the whole story.September 2026

Staying yourself

CompanyBefore the first rand: staying yourself pre-revenueThe long quiet before revenue is an information problem, not just a money one. Here is how we keep from drifting into a company we never meant to build.August 2026

Advertising

EngineeringAds without the wiring: one advertising layer for every Existence appBanners, interstitials, rewarded video, native, and app-open ads now live behind a single tested package, one interface with the network swappable underneath, off until an app asks for it.August 2026

Enterprise · Accelerated delivery

Ready to ship faster?

Tell us what you’re building and how fast it needs to exist. We’ll bring the framework, and the team that ships on it every day.

What happens next

A reply within one business day
Straight to the team, no bots in between
Enterprise access is a paid, SLA-backed licence

Tell us what needs to exist.

Want the technical detail first? Ask for docs access in the form and we’ll send it over.

Refer someone, get paid

Know a team that needs the framework? Send them our way. We pay a referral fee on every licence that closes, and you don’t have to be a client of ours to earn it.

Mention the introduction in the form and we’ll come back with the terms.

In public

Follow the work.

We build in public: releases, build logs, and the apps out in the world. One thread, what we ship, as we ship it.

X@existence_klRelease notes as they land. Ship days, live.Follow →LinkedInExistence KL CorpEnterprise notes, and the occasional opening.Follow →Instagram@existence_klcorpThe apps out in the world, real people, real moments.Follow →YouTube@Existence-KlcorpBuild logs and demos. Zero to a running app, on camera.Watch →WhatsAppExistence ChannelShip announcements, straight to your pocket.Join →TikTok@existence_klcorpThe apps in 30 seconds. Small moments, on repeat.Follow →

We’d rather show you than tell you.Prefer email? enterprise@existence-klcorp.com →

Existenceexistence