About
About Nicholic
An independent technology company, run by one person. TruXSocial is live and early; a study companion is still in early design. This page is the honest version.
Last updated
What Nicholic is
Nicholic builds technology, and researches the things it needs to understand in order to build it well. Right now that means two products: TruXSocial, a social platform that is live and in use, and a study companion still in early design.
Nicholic is one person, working from Malaysia, and it is not a registered company yet. There are no investors and no outside funding. All of that is set out further down this page rather than left for someone to discover.
What exists instead of a track record is a written one: the rules the products are being built under, published and dated before there is anything to lose by publishing them.
Build carefully. Build anyway.
The mission and the vision, and the objectives that make them checkable.
The second half of the mission is the part that does the work. Anyone can say they build new things. The constraint — only what can be made safe — is the half that can be broken in public, and therefore the half worth printing.
The objectives below follow the same rule. Each is written so that a reader could later ask "did you do that?" and get a yes or a no. An aim to be transparent is unfalsifiable and costs nothing to declare. A promise to publish changes before they take effect can be checked against dates.
- Ship nothing that cannot be made safe. Delays are announced with reasons, not absorbed quietly.
- Make money in ways users can see. How Nicholic is funded is published and kept current.
- Make leaving easy. Export and one-step deletion exist in the first release, not added later under pressure.
- Change the rules in the open. Changes are announced before they take effect, with a dated log.
- Answer people. A real person replies, within a published target rather than an implied guarantee.
- Report failures. Incidents are written up, including the ones nobody outside would have found.
- Be accountable without publishing blueprints. Commitments, funding and failures are public; architecture, infrastructure and abuse-detection thresholds are not.
Why care is an engineering requirement, not a moral pose
Ethics arguments from unknown companies are cheap, so here is the version that does not depend on anyone's character.
Software that treats the people using it as a resource to be extracted from accumulates a specific kind of debt. Dark patterns generate support load. Data hoarding creates breach exposure proportional to how much was kept. Engagement mechanics tuned against the user produce churn that has to be bought back with acquisition spend. Rules that change quietly produce the regulatory attention that eventually rewrites them by force.
Each of those is a real cost that arrives later, paid by whoever is maintaining the system. Building carefully is not a tax on building fast; it is the version where fewer things have to be undone. The two commitments in the mission are the same commitment stated twice.
How the work is done
Slowly, and in public where publishing does not create a hazard.
Decisions get written down when they are made, which is what the updates log is for. Things that are not decided are marked as not decided rather than smoothed over. Features that cannot be made safe get delayed or dropped, and the reason gets published — that is objective one, and it is the one most likely to be tested.
What research means here
It means disciplined study and careful building by one person. It does not mean a lab, a team, a publication record, or original results.
The word appears on this site because understanding a problem properly before building on top of it is most of the work. It is used in its ordinary sense, and it should not be read as a claim to anything more than that.
Independent, early, and run by one person
Being one person is a real limit. It means slower work, no cover when something breaks, and a list of promises on the principles page that Nicholic explicitly refuses to make because one person cannot keep them.
It also means there is nobody to hide behind. No committee diffuses a decision, no quarterly target makes an extractive feature necessary, and no investor is owed a return that has to come out of the people using the product. Every choice on this site is traceable to one person, and I am the one answering for them.
What Nicholic is not
- Not a registered company, yet.
- Not a nonprofit or a charity — despite an earlier name that wrongly implied it.
- Not a team. One person, no employees, no contractors.
- Not funded. No investors, nothing raised. What comes in comes from supporters.
- Not big. TruXSocial is live, and it is early.
Where things actually stand
The facts, in a table, so nothing depends on how carefully the prose is read.
| Fact | Today |
|---|---|
| Registered | No. Incorporation is intended but has not happened. |
| People | One. |
| TruXSocial | Live and in use. Early. |
| Nerdy Companion | Early design. Not usable yet. |
| Paid for by | Supporters, monthly. No advertising, no data sales. |
| Outside funding | None. No investors. |
| Country | Malaysia |
| Jurisdiction | Not decided yet |
This table is the reference for every claim on the site. If something elsewhere disagrees with this table, the other page is wrong and worth reporting.
Fair questions
›Is this a real company?
Not in the legal sense, not yet. Nicholic is one person building things and publishing the rules those things are built under. Registration is intended. Until it happens, this page says so.
›It used to be called the Nicholas Foundation. What happened?
The name was retired because "Foundation" implies a nonprofit or a charity, and Nicholic is neither. Continuing to use it would have been the first misleading thing on a site about not being misleading.
›Can one person actually build a social platform?
There is one running. TruXSocial is live, in use, and paid for by the people using it — you can go and look rather than take my word for it. That is not a claim that it is finished or large. It is the answer to whether it exists, which is the part a stranger is entitled to doubt.
›Why publish commitments this early?
Because it is the cheapest they will ever be. Adopting a constraint while small is easy; adopting it after years of growth means giving something up. Rules written now can be checked against what happens next.
›What happens if Nicholic stops?
Notice comes before shutdown, exports keep working through it, and data is deleted rather than sold as an asset. That is written into the principles page rather than left to goodwill.