Managing partners
Thirty seconds, before the first meeting.
- One email at an hour you set, not on our schedule
- A four line round-up that says whether today needs you
- Every item links to the regulator’s own page, with its own reference
Your regulators,
one digest.
RBI, SEBI, MCA and more, swept four times a day and delivered at the minute each reader sets.
- 8
- sources live today
- 4x
- swept every day, per source
- 6
- delivery times per reader
- 1 min
- scheduling precision
In use at two of India's largest law firms.
Three people sign this off. Here is each of their answers.
Knowledge management
The monitoring stops being someone’s morning.
- Everything ever sent stays searchable by regulator, phrase and date
- Read state is per account, so nothing is marked read on your behalf
- Digest history shows what went out, when, and to whom
IT and the CIO
Five DNS records. That is the whole ask.
- Nothing to install, no mailbox to hand over, no server to host
- Mail passes SPF and DKIM on your domain, so it clears your gateway
- The database refuses every direct browser read; entitlements apply server side
Regulatory news arrives late, or not at all
Every body publishes on its own terms
The RBI posts master directions, SEBI posts consultation papers, the Gazette posts scanned notifications. None of them agree on where the date lives, what a document is called, or whether yesterday’s page still says what it said. Checking them by hand is somebody’s morning, every morning, and the morning it gets skipped is the morning something moves.
Three of them actively resist being read
The MCA refuses clients that are not browsers. MeitY renders its list after the page loads, so fetching the HTML returns nothing. The e-Gazette needs a form postback before it will show a result at all. A feed reader gets none of these, which is why they are the three most often missed.
A generic round-up lands in quarantine
It arrives on the sender’s schedule, covers whatever the sender chose to cover, and comes from a domain your mail system has never seen. What a practice needs is its own sources, on its own clock, from an address its own IT already trusts.
Coverage
What is read, and what comes back
Each source reports how it is fetched and how hard it is to keep working. A firm is licensed for the ones it pays for, and the rest never reach its console, its search or its mail.
RBI
Reserve Bank of India
Circulars, notifications, master directions, press releases
High volume, several sections, dates in more than one format.
Direct requestlow
SEBI
Securities and Exchange Board of India
Circulars, consultation papers, orders, informal guidance
Intermittently slow to answer from outside India.
Direct requestmoderate
MCA
Ministry of Corporate Affairs
Notifications, circulars, amendment rules
Blocks clients that are not browsers, so it is fetched as one.
Headless browsermoderate
IBBI
Insolvency and Bankruptcy Board of India
Circulars, regulations, discussion papers
Steady, but files are named inconsistently between sections.
Direct requestlow
IFSCA
International Financial Services Centres Authority
Circulars, guidelines, consultation papers
Small volume, easy to lose inside a broader financial feed.
Direct requestlow
MeitY
Ministry of Electronics and Information Technology
Notifications, rules, advisories
Builds its list in the browser, so the raw HTML is empty.
JSON APImoderate
PIB
Press Information Bureau
Releases across every ministry
Very high volume, filtered down to what a practice would read.
Direct requestlow
e-Gazette
The Gazette of India
Ordinary and extraordinary gazette notifications
Needs a form postback before it returns anything at all.
Headless browserextreme
Need one that is not on the list?
A source is one module in the crawler, so adding one is ordinary work rather than a new product. Firms have asked about CBIC, CBDT, the CCI, IRDAI, TRAI, CERT-In and the courts. Tell us which ones matter to your practice.
From a government page to your inbox
Sweep
02:00, 07:00, 12:00 and 17:00 IST
Every source is fetched four times a day. The two that refuse ordinary clients are fetched through a real browser instead, on rotated keys so one running out of credit does not stop the run. A third is read through the JSON API behind its site.
Compare
On every sweep
Each item found is compared against the one already held, field by field. If nothing changed, nothing is written. That is what stops a page being re-rendered by the regulator from resurfacing as a fresh update in somebody’s inbox.
File and index
As each item is stored
Items are filed by regulator and by kind, and indexed for search across titles, summaries and the issuing ministry. Query words are stemmed the same way, so a search for one form of a word finds the other.
Send
At each reader’s chosen minute
Everything since that reader’s last digest is grouped and sent as one email, from the firm’s own sending domain where that is set up. If nothing is new, no email goes out at all.
What arrives, from the subject line down
Subject line and preheader
The subject names the edition and the date. The preheader, which is the grey line the inbox shows next to it, counts the updates and names the regulators, so a reader can decide whether to open it without opening it.
In this round-up
A short table at the top: each regulator with a count, and a total. It is the whole digest in four lines, and it is what a partner reads on a phone between meetings.
A section for each regulator
Sections appear in a stable order and carry the firm’s accent colour. A regulator with nothing new is left out entirely rather than shown as empty.
Each item, with what it is
The kind of document is labelled above the title, so a circular is not mistaken for a consultation paper. Below that: the summary where one exists, the date it carries, and a link that goes to the regulator’s own page rather than a copy.
A footer that behaves
The firm’s reply address, a link into the portal, and a one-click unsubscribe that works from the button Gmail and Outlook put at the top of the message.
Built for mail clients, not browsers
Tables and inline styles throughout, because Outlook renders with Word’s engine and Gmail strips the stylesheet. It is 620 pixels wide, which is what survives both.
The digest is the summary. The portal is the record.
Everything ever sent stays searchable, filed by regulator and by date, for the weeks when a matter turns on when something was issued rather than on what it said.
- Overview
- Counts for the period, the sources that moved, and the last digest sent: when it went, who received it and what was in it.
- Updates
- Everything the firm is licensed for, newest first, with search across titles, summaries and ministries, a date range, and a filter by regulator.
- Categories
- One regulator at a time, for the weeks when a matter turns on a single body and the rest is noise.
- Notifications
- What has arrived since you last looked. Read state is held against your account, so a colleague reading an item does not mark it read for you.
- Email digest
- Your delivery times, the sources you want in the mail, and any other recipients you copy.
- Administration
- For the platform operator only: the firms, their accounts and roles, the sources each is licensed for, and which domain each firm’s digest is sent from.
- SEBIPublic issues19 Oct
Zetwerk Manufacturing Businesses Limited : Addendum to RHP
- RBIPress release19 Oct
Money Market Operations as on October 18, 2026
- IFSCATender19 Oct
Notification on Vacant Space for 8th Consideration Period (16.10.2026 to 30.11.2026 ) for RFP Ref No. IFSCA-Admn0IHBP/9/2025-GA dated 02.01.2026
Delivered when the reader wants it, not when we run
The sender wakes every minute and asks who is due, so a delivery time is a real time rather than the nearest slot to it. All times are Indian Standard Time.
- Any minute, up to six a day
- Not three fixed slots. A reader can take 06:54 before the commute, 13:10 after lunch and 17:45 at close, and change them whenever they like.
- Typed however you type it
- The time box accepts 6.54am, 6 32am and 555am as readily as 18:45, because nobody should have to learn a format to change when their mail arrives.
- Other recipients, their own rules
- A partner can copy an associate on the morning send only, and give them a narrower set of sources than their own.
- Nothing new means nothing sent
- A quiet morning produces no email. A digest that arrives empty trains people to stop opening the ones that are not.
Accepted
- 06:54
- 6.54am
- 6 54am
- 654am
All four set the same delivery time. Nobody should have to learn a format to change when their mail arrives.
The digest arrives looking like yours
Mail from a sender your people have never seen gets held at the gateway, however well configured the sender is. Point a subdomain of your own domain at us and the same digest arrives from your firm, carried by a name your own mail system already trusts.
From
digest@lexcalibre.site
Quarantine
A vendor domain your mail system has never seen.
From
digest@updates.yourfirm.com
Inbox
A subdomain of yours, which your gateway already trusts.
We register the subdomain
A subdomain of yours, never the domain itself. Verifying the domain would let this platform send as anyone at the firm, which is more than the job needs and more than your IT should agree to.
Your IT publishes five records
Three CNAMEs for DKIM, an MX and a TXT for the return path. They are issued in the console ready to copy, and nothing about your existing mail routing changes.
We check, then switch
Sending moves only once the records are confirmed live. Until then the digest keeps arriving from our domain, because mail from an unverified one does not arrive at all.
For your IT: the five records, and what they do
Three CNAMEs let us DKIM-sign as your subdomain. The MX and TXT put the return path there too, so SPF passes on your domain rather than ours, which is the alignment DMARC actually inspects. Nothing about your existing mail routing changes, and sending stays on our domain until every record is confirmed live.
Issued for yourfirm.com
| CNAME |
| DKIM signing |
| CNAME |
| DKIM signing |
| CNAME |
| DKIM signing |
| MX |
| Return path |
| TXT |
| SPF |
Deliverability
Why it reaches the inbox and stays there
SPF that aligns
The return path sits on a subdomain of yours rather than on the sending service, so SPF passes on your domain. That alignment is what DMARC actually inspects.
DKIM on three keys
Every message is signed. Three keys are published so one can be rotated without a gap in signing.
One-click unsubscribe
The RFC 8058 headers are set, so the unsubscribe button Gmail and Outlook render at the top of the message works, and counts in your favour with both.
Suppression that sticks
A hard bounce or a spam complaint removes that address immediately and records the reason the receiving server gave.
What happens when something breaks
A source that quietly stops answering
Failures are counted per source across recent runs rather than in aggregate. A source failing repeatedly raises an alert, because a source that has silently stopped looks exactly like a quiet week.
A mailbox that has been closed
The bounce is recorded with the reason the receiving server gave, and the address is suppressed. A dead mailbox never quietly drains the sending reputation the rest of the firm depends on.
A reader who marks it as spam
That address is suppressed at once. Nobody is mailed again after asking not to be, whichever way they asked.
A busy hour at the regulator
A transient failure is noted but does not suppress anything. The next sweep picks the update up, and a bad ten minutes on a government server does not cut a firm off.
What your IT will want to hear
- The database is sealed to browsers
- Every direct client read and write is denied. All data is served through server routes that use an admin credential the browser never sees, so the public client key grants nothing.
- Every request proves who it is
- Each call resolves the caller and their firm from a Firebase token. A request without one is refused rather than served a default view.
- Licensing is enforced on the server
- A firm’s entitlements are applied where the data is read, not hidden in the interface. A source the firm is not licensed for is not returned to it at all.
- Reading is not shared
- Read state is keyed to the individual account. One firm’s reading activity is never visible to another, and not to colleagues either.
What setting up actually involves
The firm is created
Its name, accent colour and reply address, and the sources it is licensed for.
Accounts are added
One per reader, with a role. Nothing is installed and no mailbox is handed over.
Readers set their own times
Each person picks when their digest arrives and which sources are in it.
Sending moves to your domain
Optional, and can be done later. Five DNS records, then a check before anything switches.
Questions a firm asks before signing
How quickly does an update reach us?
Every source is swept four times a day, at 02:00, 07:00, 12:00 and 17:00 IST. Anything found in a sweep goes out with your next scheduled digest, so the wait is your own delivery time rather than ours.
Can two people at the firm read it on different schedules?
Yes. Delivery times are set per reader, up to six a day, and each reader can unsubscribe without affecting anyone else. The sources a firm is licensed for are set once, for the firm.
What happens when a government site is down?
That sweep fails and the next one picks the update up. Repeated failures on one source raise an alert, because a source that has silently stopped looks exactly like a quiet week.
Do we get the document itself?
Every item links to the regulator’s own page. Nothing is rehosted, so what you open is the official copy with its own reference number, and a citation points where a citation should.
Can the digest come from our domain?
Yes. Your IT publishes five DNS records on a subdomain of yours and the mail then passes SPF and DKIM on your domain. Until they are live the digest keeps arriving from ours, so there is no window where mail stops.
Why a subdomain and not our main domain?
Verifying your main domain would let this platform send as anyone at the firm. A subdomain is enough for the digest and is the only thing we will ask for.
What does the firm have to run?
Nothing. There is no agent to install, no mailbox to hand over and no server to host. The only setup work is the five DNS records, and only if you want your own sending domain.
Can we add a regulator later?
Two different answers. One already on the list is a change to your entitlement, and it appears in the console and the next digest together. One not on the list is a new module in the crawler, which is ordinary work rather than a new product. Tell us which and we will say how long.
Does anyone else see what we read?
No. Read state is held against the individual account, and a firm only ever receives the sources it is licensed for. That filtering happens on the server, not in the interface.
What if a reader marks it as spam?
They stop receiving it immediately and the reason is recorded. Nobody is mailed again after asking not to be, whichever way they asked.
Tell us what you want tracked.
Access is arranged per firm rather than signed up for, so the first step is an email. Four things in it and we can answer properly rather than asking you the same questions back.
- Which regulators you want tracked, including any not on the list yet
- How many people should receive the digest
- The hours that suit them, if you already know
- Whether you want it sent from your own domain
Write to
hello@lexcalibre.siteRead by the people who run the platform. Replies come from the same address.
Request accessAlready set up? Sign in to the portal