The whole stack
Seven systems, one account,and the job each one does here.
castoMIND has no features of its own worth listing. Everything it produces is produced by another member of the castomo family, and its contribution is knowing which one, when, and with what. This page is the map: every part, and what it contributes to a product that did not exist this morning.
Each of these sells on its own, to its own customers, with its own website. None of them was built for castoMIND. What castoMIND adds is that all seven can be driven at once, by one thing, on one account — which is a fact about who owns them rather than a fact about software, and it is the whole reason an hour is enough.
The building half
Three systems that make the product exist.
castomUI
The website. Generates and publishes the marketing site for the new product — pages, copy, brand, live at an address. Not a template with your colour in it: the copy comes from the written case produced at stage two.
Learn moredash-b
The dashboard. A live dashboard designer, in 86 languages, that lays out the board the product will be run from. It goes up before the first customer, so month one has numbers in it.
Learn morecastomFLOW
The machinery. Builds the workflows that do the repetitive work: order to invoice, the day-three follow-up, the nightly job. AI on the steps that need judgement, and pointedly not on the ones that do not.
Learn moreSeven products would be seven invoices.
This is one.
The customer half
Three systems that make somebody notice.
iKonekt
The CRM. Every channel into one inbox — chat, forms, e-mail, phone, call-me, QR — each arrival a contact with a source and an owner from the second it lands, and a pipeline that runs through to a KSeF invoice.
Learn moreclickSomo
The campaign. Marketing automation across e-mail, SMS, push and printed letters, as funnels with triggers, so the second message depends on what the first one did.
Learn moreFABLS
The visibility. Automated blogging and social accounts: writers, a three-to-six month plan, posts published on schedule, weekly and monthly reports on what it produced.
Learn morecastomAPI,
underneath all six.
The platform layer the whole family stands on, and the reason none of the six above has to buy anything in. It is not a product in the pipeline so much as the floor the pipeline walks on.
34.8 million rows of public reference data — countries, currencies, languages, 13.4 million places, two million postal codes, airports, seaports, vehicle makes. More than 175 live event sources. A royalty-free media library searching eleven providers, importing with licence and attribution attached. And the services: send, SMS, push, booking, payments, short links.
Why this matters at hour one: a new product usually cannot take a payment, send an SMS or use a photograph legally in its first week, because each of those is an account, a verification and a wait. Here they are already there, on the account you already signed into.
- ◆Reference data34.8M rows. Validate an address, resolve a place, check a currency code.
- ◆Events175+ live sources, refreshed continuously, each carrying its licence.
- ◆MediaEleven providers searched at once; the credit line generated from the record.
- ◆SendE-mail, SMS and push with one shared delivery vocabulary.
- ◆Book and payOffer a slot, hold it, confirm it. Take a payment, watch the webhook.
- ◆LinksShort links with counted redirects and no tracker in sight.
No keys to rotateNothing external needed
The arithmetic of one owner.
Assembled from separate vendors, this list is seven sign-ups, seven billing relationships, seven support routes, seven sets of terms, and — the expensive one — six integrations that somebody has to build and then keep alive as each vendor changes its mind. Every founder who has done it knows the shape: the stack works for four months and then something moves.
Owned by one company, it is one account, one wallet, one invoice, and a set of services designed to sit on the same shelf and speak the same event vocabulary. There is nothing to integrate because there was never a gap.
That is the plain reason castoMIND can exist. It is not a cleverer orchestrator than somebody else could write; it is an orchestrator that is allowed to drive every system it needs, without asking a vendor for API access and waiting a fortnight for an answer.
And castomo,
over the top.
castomo is the house all of this sells through — the company, the single account, the single wallet, the sign-in that works everywhere in the family. If you already use one of the products above, you already have the account the whole pipeline runs on.