Customers, suppliers, partners, your own colleagues, your board. Each of them logs in on your domain and sees only what concerns them, taken live from the systems you already run. Kilango stores none of it.
Kilango is invitation only while we grow. Tell us who you are and we will come back to you.
Three customers, three businesses, the same product. Each portal shows something different because there are different systems behind it.
An app in Kilango is a system you work in every day. You connect it once and turn it on for the portals it belongs to.
A person gets access to one portal as part of an organisation. The organisation is linked to a record in your system, and that link decides what comes through.
When a customer says they cannot find their report, you look at their screen. The session is read only, lasts 15 minutes and shows up in the activity log.
Kilango is also a native iPhone app. The same access, the same brand and the same pages.
The app carries the brand the portal has: mark, colour and name. Kilango is the platform, not the front.
A widget is built once and shows up both places. The phone beside this text renders the same widgets as the portal in a browser, not a separate mobile version of it.
Native screens composed from the same widgets as the web portal — not a website in a frame.
The app is on its way to TestFlight. The portal in the browser works today.
Some of these face outwards and some face inwards. Which one you get is decided by the systems you connect and the people you invite, and you can run several side by side.
Status, deliveries, invoices and agreements, for each customer on their own.
Where a case stands, which documents are signed and whose turn it is. For advisers, agencies and firms.
Orders, deliveries and settlement, out to the companies that deliver to you.
Hours, equipment and documents, without standing up another intranet.
Prices, material and pipeline, for the people who sell on your behalf.
Progress, drawings and handovers on the individual project.
No import, no synchronisation, no copy. A widget asks your system when the page is opened, the answer is rendered, and then it is gone. Most portal products want to become the system. We do not, and that is the one thing they cannot write.
That is the whole record. No contacts, no notes, no history, and no copy of anything your own system holds. There is no table it could go in, and a build fails if anyone adds one.
How it is enforcedOnce the invitation is there, it is three steps, and you do them yourself.
Your logo, one colour and your own domain. Kilango derives the rest, so the portal looks finished from the first screen.
Pick the systems your customers ask about and sign in to them. Kilango finds the customers and projects that belong together.
Send the first login. Everyone else gets the same portal with only their own information in it.
Kilango is invitation only while we grow. Tell us briefly who you are and what your customers keep asking about, and we will come back to you.
Already invited? The way in is in your inbox. Log in.