A Logging Solution with a Collaborative Vibe
Most logging tools were built for a single company, a single system, and a single team. They create isolated, context-free log streams that consume massive storage and require complex, expensive tooling just to extract basic insights. The result? High cost, slow analysis, and value that rarely extends beyond IT. But modern applications don’t work that way.
Modern applications are composite by design. They are web-based, API-driven, and deeply dependent on third-party SaaS and PaaS services. Yet logging remains siloed. Service providers have no structured way to share relevant log data with their customers, and customers lack visibility into how dependent services actually behave. As applications and platforms become more interconnected, this fragmented visibility slows developers, overwhelms support teams, and makes diagnosing issues across service boundaries unnecessarily painful.
Microlog is a modern logging service built specifically for PaaS and SaaS providers.
Designed from the ground up with a secure, multi-tenant architecture, Microlog introduces collaborative logging
(
Log space is logically divided into logboxes, by service providers or clients,
like mailboxes.
Log messages are organized into logboxes, like emails.
No more looking for a needle in a haystack.
Custom settings per logbox.
Open, distributed.
Multi-tenant with
Messages are directly logged and searched in the client logbox.
IT, business, product, support staff, and clients can access log messages on
the Microlog Admin Portal (WAP), or via API (Engineering).
WAP is a responsive web-app. You can search and view log messages on your mobile devices.
| Feature | Description | Benefit |
|---|---|---|
| Logging Model |
Two simple REST APIs, write or search, for interacting with a logbox. Support |
With |
| Web Admin Portal |
Each service provider or client creates an account with multiple R/W or R/O administrators. They manage their accounts, logboxes, admins, search and view reports on WAP. Custom logbox settings include message retention period, size limit, integrity checks and more. Search other connected accounts' logboxes, but restricted to only the messages you logged. Manual logging feature facilitates initial trial and error phases without using API. |
Increase flexibility and productivity. |
| Message Security and Integrity |
Data is hardware encrypted at rest and SSL encrypted in transit. Log message integrity is ensured by keyed-MD5 or public signatures. |
Encourage high value information exchange. Enhance Provider-Client relationship beyond basic API functionality and response code. |
| Provider-controlled Client Involvement | With progressive level of participation, providers can start their clients with no account, to a provider-managed Proxy account, and finally an independent client-managed Primary account. | Take advantages of Microlog even without direct client involvement. |
Step 1
Whether you are a service provider or consumer, create your primary account, log in, and complete the OTP verification.
Step 2
If you are a provider, create a proxy account to represent your client.
Step 3
It lists yours and other connected accounts. Look for your client's account (Proxy account).
Step 4
Click on the Proxy Account's logbox name. You can change the logbox settings, manually log a message, or search the logbox by setting various filters on/off.
Step 5
Typically this is done with the API, but for illustration purposes we will use the manual logging feature to show how a message is logged, while still using the API underneath.
Step 6
Once you are back to the Logbox page, click on Search, and you should see the new log message.
Step 1
Whether you are a service provider or consumer, create your primary account, log in, and complete the OTP verification.
Step 2
If you are a provider, create a proxy account to represent your client.
Step 3
It lists yours and other connected accounts. Look for your client's account (Proxy account).
Step 4
Click on the Proxy Account's logbox name. You can change the logbox settings, manually log a message, or search the logbox by setting various filters on/off.
Step 5
Typically this is done with the API, but for illustration purposes we will use the manual logging feature to show how a message is logged.
Step 6
Once you are back to the Logbox page, click on Search, and you should see the new log message.
Years ago, while experimenting with the Twilio API, I hit a wall of baffling errors. The moment I logged into my dashboard, I was met with real-time logs that pointed directly to a missing HTTP header. The fix took seconds. I didn't just feel relieved; I felt empowered.
Recently, I saw the other side of that coin with my Oura ring. When I contacted support about a connectivity issue, the representative didn’t read from a script. They instantly accessed the ring’s activity logs, diagnosed a hardware failure, and shipped a replacement immediately.
These moments revealed a critical gap in how logging technology was built: log data is most powerful
when it is "hot", context-rich, and democratized. For too long, vital system insights have been locked in backend silos,
accessible only to IT specialists. We realized that the key to ultimate customer satisfaction is
making this data directly client relevant. Whether it’s a consumer troubleshooting their own device or a frontline worker
solving a high-stakes problem, the data needs to be accessible, organized, and lightning-fast.
Microlog was founded to change that. We build client-centric logging solution with a collaborative models that turn cold, isolated data into "hot" insights with contexts, making system behavior transparent, user-facing model accessible, and analysis lightning-fast to solve problems before they become frustrations.
Microlog is a cloud logging service that is designed for
It works like email messages and mailboxes, but instead we have log messages and logboxes.
One particular feature,
Each service provider and client will have their own account, and if they are connected, can log and search messages in each other's logbox, much like sending an email to your friend's mailbox.
Microlog is installation free, user and mobile friendly, and easily accessible on the Web Admin Portal even by the non-IT teams.
During the first login after creating an account or resetting your password, a One-Time Passcode (OTP) will be emailed to you. While this typically arrives instantly in Gmail, users of other providers like Yahoo! should check their junk or spam folders if the email does not appear in the inbox.
Microlog's
Provider simply logs messages in its own logbox, identifying the client in the client tag of the write-log API, then use the same value in the client tag when searching in your own logbox.
Provider creates a Proxy account to represent a client, and log messages directly in the proxy account's logbox. A Proxy account is login-disabled, solely owned and managed by the service provider.
Provider "promotes" the proxy account to a full-function account, because the client wants to take back ownership
and be able to log in, log messages, search logboxes, and connect with other service providers for
Each logbox has a name and the default name is
Also, if you skip the logbox name argument in the API, it will default to your own logbox name.
You refer to the logbox of a connected account by its name in an API. But if the name is changed by the owner you may wonder if your API will still work. Also, there are times you may want to have a different name, or names, to refer to a logbox but you can't because it is owned by a different account and you can't rename it.
When two accounts are connected, a default alias is created on each account to refer to the logbox of the other account using the name at the time of the connect and its immutable ID. This means even if one of the names is changed later APIs using the old logbox name will still be able to reach the logbox via the ID.
You can create an alias (or multiple aliases) to an external logbox too. For instance, you can create an alias using the client's account ID in your system, and another using the API key used to access your services.
You can manage logbox aliases on the Microlog portal.
Microlog stores log data in hardware encrypted store and transmitted them over SSL to the destination. Log message integrity is protected with default keyed-MD5 scheme or public signatures.
When using an API, the API key you choose (prefixed with either "test_" or "live_") in the authorization header determines if the API is going to be executed in the test or live environment.
When using the Microlog portal for "Manual logging" or "Search with filters" the "test or live" message type is presented as a radio button on the form.
Again, only the test API key is offered during the soft launch.
The controls are on the Microlog Portal.
If you are using the Search API, resultsz are returned in pages, and you can navigate to the remaining pages based on the "more" attribute in the results: true means there are more pages otherwise this is the last page (refer to the downloadable Microlog REST API Collection PDF for the use of page_number.
Go to Account profile on the portal to adjust query_page_size to control the max number of results per page, and max pagination depth to control the number of pages you can navigate. Both have predefined limits.
If you are using the "Search with filter" feature on the portal, you can only control the default number of results returned per search and the UI will be responsible for pagination.
Go to User profile on the portal to adjust the default number of results returned per search. This value will then be used as the default on the search page but you can dynamically adjust it further up or down as long as it is within the max allowable limit.
Yes, Microlog is a SaaS service and can integrate with various platforms and systems via a couple simple REST API for logging and searchingx.
Our next releases will include AI capabilities such as agentic logging, smart classification and space management.
During our soft launch, customers can use the Test API key for free and email tech@microlog.io for support.
Microlog API can be used in test, sandbox, or production environments, capturing successes, failures, exceptions, remedies, and audit trails during processing of client requests. It can also be applied to selective clients, or for particular types of product launch (e.g. Beta).
