Skip to content

Unlisted Basket

Discover India's Unlisted Shares

See the unlisted shares this business offers, the price it published and the date it published it, and ask about availability before you agree to anything. Prices here are the business's own, not exchange prices.

Explore SharesTalk to an Expert

No share is listed here yet.

How it works

Four steps, agreed in writing before anything is paid

The process is the same for every share on this page. Anything that differs from it is agreed in writing before it happens, and not before.

  • Choose a share

    Look through the shares on this page, and open a share's own page for everything this business publishes about it.

  • Send an enquiry

    Tell the team which share you are asking about and how to reach you. An enquiry is a question, not an order.

  • Agree availability, price and terms in writing

    The team answers what is available, at what price and on what terms, and puts it in writing. Nothing is agreed until it is written down and both sides accept it.

  • Transfer and payment, in the order you agreed

    The share transfer and the payment follow the steps the written terms set out. The business does not ask for money before those terms exist.

Why this business

The four things this page can stand behind

They describe how the business works, not what a share will earn.

  • Published prices carry their date

    Where the business has published a price, the card shows that price and the day it published it. A price with no date beside it is not shown as a current price.

  • A dealer's quote is called indicative

    A provider's quote is labelled indicative, attributed to the source that gave it, and never presented as an exchange price or as a price the business has published.

  • Terms come in writing before payment

    Availability, price and terms are put in writing and accepted by both sides before any money moves.

  • One team answers

    The same team answers the question about a share, the written terms, and what happens after they are agreed.

Fees

This business has not published a fee schedule here, so this page does not publish one either. The charges that apply to a transaction are confirmed in writing before anything is paid.

The written terms say what is charged, what it covers and how it is paid. If those terms do not suit you, the transaction does not go ahead.

    About

    What Unlisted Basket does

    Unlisted Basket is an unlisted-share business. It lists the shares it offers, publishes the price it has set for a share and the date it published it, and answers enquiries about buying them.

    Dealing in unlisted shares is a private transaction, not an exchange trade. The buyer and the seller agree availability, price and terms between themselves, and the business writes those terms down before anything is paid.

    Nothing on this site is investment advice. A share's value can fall, and a buyer may have difficulty selling it on, because there is no exchange on which it trades.

      Questions

      Frequently asked questions

      Short answers to the questions this business is asked most. If your question is not here, ask it in the form below and the same team will answer.

      • What is an unlisted share?

        A share in a company that is not listed on a stock exchange, so it is bought and sold by private agreement rather than on an exchange.

      • Where does the price on a card come from?

        It is the price this business published, and the card shows the day it published it. A provider's quote is a separate figure, marked indicative and attributed to its source.

      • How do I start?

        Send an enquiry naming the share you are asking about. The team replies with what is available and on what terms, in writing, before anything is agreed or paid.

      • Can I sell the shares later?

        A sale depends on finding a buyer and on the company's own transfer rules. There is no exchange to sell on, so a sale can take time or may not happen.

      Risk disclosure

      The risks you are taking

      Read this before you enquire about any share on this page. These risks do not go away because a price is published or a team is helpful.

      • Unlisted shares are not exchange-traded

        There is no stock exchange price, no order book and no exchange settlement for these shares. Every price is the business's own or a dealer's, and every transfer is a private arrangement.

      • They can be hard to sell

        Unlisted shares are illiquid. A buyer may not be available when you want one, and the company's transfer rules can delay or prevent a sale.

      • A quote is indicative, not a guarantee

        An indicative dealer quote is one dealer's view on one day. It is not an offer to buy or sell at that figure, and the price finally agreed can be different.

      • No assured return and no listing gain

        No return is promised, and no listing is promised. A company may never list, may list later than expected, or may list at a lower value than you paid.

      • Verify before you decide

        Check the company's filings, its financial statements and the share transfer terms yourself, or with an adviser you choose. Nothing here replaces that check.

      Ask about a share

      Name the share you are asking about and how to reach you. The team replies with what is available and on what terms, in writing, before anything is agreed or paid.

      Email
      earlybakefinserve@gmail.com
      Telephone
      +91 8368938052
      Office
      126, Manglam Paradise Mall, Sector-3, Rohini, Delhi-110085
      Business hours
      Monday to Saturday, 10:00 AM - 7:00 PM IST
      Call +91 8368938052

      Send us a message

      Tell us what you need and we will reply by email.

      The name you would like us to use.

      The address we should reply to, such as name@example.com.

      Optional. Digits and spaces only.

      What you want to know about the shares we offer.

      Downloads

      Android and desktop apps

      Download the native Android app or the Windows desktop app. Every published version is listed with its release date, its changes, its file size and its SHA-256 checksum, so the file you receive can be checked against the file that was released.

      • Android

        Android app

        The native app for Android phones and tablets, signed with the product release key. Download the package directly; no store account is needed.

        Current release

        1. 0.1.2

          Released

          • Live talk reaches a camera: the phone opens a talk session, sends its microphone to the camera over WebRTC, and offers mute, hold and close. The audio peer joins only when a camera host answers; when none does, the session says so instead of pretending it is connected.
          • The Android download is now one package per phone processor: a 32-bit phone downloads the 9.6 MB package built for it, and a newer 64-bit phone the 15.1 MB one, instead of every phone carrying every processor's native libraries.
          • Events are on the phone: the list shows what happened at each camera, and a person can acknowledge an event and then resolve it, with the server recording each step.
          • Camera care is on the phone: a saved position is written to the camera's own preset list, and a movement command is refused in words when the camera has never answered.
          • Sharing is on the phone: a share link is created and shown once, access is granted to an address, and a zone can be switched on or off, all against the module's own rules.
          • The video wall and viewer layouts are on the phone: a display opens its tiles into a real viewing session, and a layout can be created or edited and saved.
          • Patrol and reports are on the phone: a run starts, an observation is added, the run completes, and a report runs on the server from the phone.
        Earlier versions (2)

        1. 0.1.1

          Released

          • The Android package is rebuilt from a changed native version input, proving that one native change produces a new published version, a new signed file and a new permanent download address.

        2. 0.1.0

          Released

          • The first signed Android build of the product is published: the native app for phones and tablets, with the existing camera slice, sign-in and the bilingual shell.

      • Desktop

        Windows desktop app

        The native app for Windows. Download the package, unpack it, and start the app; the Windows runtime and UI toolkit are used from the machine rather than carried a second time.

        Current release

        1. 1.0.0

          Released

          • The first Windows desktop build of the product is published: the native WinUI app with sign-in, the shared shell and the camera list.

      A download appears only when a real build exists. A platform with no release says so in words and offers no button.

      Android and desktop apps

      • Server

        1. 1.9.27

          Released

          • The surveillance workspace now names its KYC review desk, and the reviewer permission is granted by the role seed.
          • Reviewers reach the queue and profile decisions; ordinary accounts are refused, and own KYC stays separate.

        2. 1.9.26

          Released

          • Declared form-group catalogue prices, the refund admin queue and buyer wording, and the showcase control entrance.

        3. 1.9.20

          Released

          • The shared landing footer keeps the caveat, tagline and links inside the brand column at 320px and 200% text, so the phone page no longer widens. The footer caveat remains part of the footer rather than a white strip above it.

        4. 1.9.18

          Released

          • The module's honest caveat now sits inside the footer under the product line, instead of a separate white strip between the sign-in band and the footer. The footer and the caveat are one surface, and the old standalone footnote is gone from every shared landing page.

        5. 1.9.17

          Released

          • The shared live player uses the HLS engine where available so the media token is sent as an Authorization header on every stream request; the native fallback stays for browsers without that engine.

        6. 1.9.16

          Released

          • The Billing accounts screen keeps the provider verification result after the check, instead of replacing it with the previous unverified list row.

        7. 1.9.15

          Released

          • The recurring mandate now ends inside the provider's 30-year validity instead of asking for 100 years, so UPI Autopay and card authorisation can complete.

        8. 1.9.14

          Released

          • A safe Billing accounts screen lists each configured payment connection with its provider, mode, approval, plan and webhook readiness, and a Verify button that checks the provider plan. It has no field for a key or a secret.

        9. 1.9.13

          Released

          • A billing account whose provider or domain approval is pending or suspended no longer receives a gateway, so it cannot open a checkout or accept a notification. The safe account list names the approval state.

        10. 1.9.12

          Released

          • Administrators can list the configured billing accounts and check an account's plan with its provider. The answer states only safe facts - whether a plan or webhook secret is present and whether the provider accepted the check - and never returns a key id or a secret.

        11. 1.9.11

          Released

          • The release history now shows each release's exact India time beside its date in both languages; the shared landing package is rebuilt before the client so the deployed page carries the change.

        12. 1.9.10

          Released

          • Every release in the version history now shows the exact India time beside its date, in both English and Hindi, so two releases on the same day can be told apart.

        13. 1.9.9

          Released

          • Billing accounts now own their gateway connection and webhook signature, so a second account cannot act through the platform account.
          • A subscription, its charges and its payment events now carry the billing account that owns them, and a verified notification cannot change another account's subscription.

        14. 1.9.6

          Released

          • The refund ground is now a required closed set: a refund is accepted only for a duplicate charge, a service that was never delivered, or a charge taken after a cancellation. The server refuses any other reason and the existing refusal shape is unchanged.
          • The detection-zone dialog, the upload page and the camera-consent dialog now use the shared form page and field owners, with numbered sections, an error summary, the module's own refusal and a server-confirmed result.

        15. 1.9.5

          Released

          • Email-code sign-in is live: the shared sign-in form offers a password or an email code, with separate accessible hints for the address and the code, a server-stated code length and resend wait, a generic answer for every address, and the same session handoff as the password route. Password sign-in is unchanged.

        16. 1.9.3

          Released

          • Email OTP server, the subscription buyer screens, OpenRouter free-model AI routing and the latest surveillance form/list screens are included. Email OTP sign-in screen is not yet part of this release; password sign-in is unchanged.

        17. 1.9.2

          Released

          • Security-layer and billing maintenance: the tenant-scoped billing subscription schema is in place, and the server-side Razorpay integration is included but disabled until configured. No price is charged.

        18. 1.9.1

          Released

          • Core scheduler retention duties, fail-closed tenant policies, the bounded diagnostics ingest and the shared form-owner screens are deployed.

        19. 1.9.0

          Released

          • The module resolves its tenant from the request host before sign-in, and the tenant's stored brand, display name, support contact and colour roles are painted on its own sign-in and workspace pages. Tenant administration, invitations, the catalogue with plans and orders, entitlements, export and deletion are part of the release, and row-level isolation fails closed instead of falling open to the platform tenant.
          • Twenty more surveillance screens are declared once in the module's form contract and render through the shared field, selector and button owners. Sign-in asks for a second factor only when the server says one is required, and the account list states whether each account holds an active factor.
          • App-lock and attestation challenges are connected to the sign-in chain, so a locked app does not open without the server's verification. The surveillance media chain keeps one gap-free recording timeline under concurrent appends, and a recording still missing its upload after 24 hours becomes Failed with RecordingUnavailable instead of Complete.
          • The web and native clients carry the 320px and 1280px navigation, brand and read-frame fixes, and the public landing offers Android 0.1.2 for both phone processors: arm64-v8a at 15,094,074 bytes and armeabi-v7a at 9,620,390 bytes, each with its checksum.

        20. 1.8.5

          Released

          • The surveillance module resolves its tenant from the request host before sign-in: an unknown host answers 404, a suspended tenant 403 and an archived tenant 410, and a tenant cannot be chosen by a request header.
          • The tenant directory is the module's own: six management routes and one public read, two permissions, and row-level isolation in the module's own database. The platform tenant answers on cam.pehromgroup.com and on the loopback addresses this machine's clients use.
          • The NAS recordings browser and player are live: configurable SMB or folder sources, range streaming, H.264 playback, H.265 transcoding, thumbnails and download, in English and Hindi at 320px.

        21. 1.8.3

          Released

          • The surveillance server publishes the report and layout kinds, revokes an older share link by id, names the release state and labels, enforces two-person approval, publishes integration kinds, the storage policy and attachable uploads, and records camera-host capabilities.

        22. 1.8.2

          Released

          • The workspace gains the video wall, notification preferences and the upload screen, and the web client now uses the one generated frame with no duplicated keys.

        23. 1.8.1

          Released

          • The workspace gains a self/device camera: the camera on the machine you are using can be previewed live, with its own permission and a release when you stop or leave. No recording and no upload.
          • The reset screen and its mail configuration are carried in the same release.

        24. 1.8.0

          Released

          • The surveillance catalogue reads answer from the module own rules: alert event kinds, location node kinds, analytics rule kinds, camera command kinds, privacy mask effects, maintenance windows, investigation owners, upload options and storage coverage.
          • A maintenance window now has a real end beside its promised end, and the billing seed follows the permission catalogue so the seeded roles hold every permission again.
          • The password-reset mail is configured with the domain sender, and a bilingual reset screen accepts the link and sets the new password.

        25. 1.7.0

          Released

          • The camera's own machine now drives the camera: the agent opens it, learns what it is and what it can do, reads its streams, steers it, reads its presets and its firmware, and starts and stops its recording. The camera's own credential stays on the camera's machine.
          • The module now publishes a signed release for a camera host to take, and the host learns of a recording to make on its next poll: the module asks, the host makes it, and the module records what became of it.
          • The protocol's own wording has one owner in both languages, so the module that signs a release and the host that verifies it cover the same bytes - which is why the engine's contract moved from version 2 to version 3 and a module on the old library now refuses to start.

        26. 1.6.0

          Released

          • The camera's own machine now runs an agent that answers for it: the protocol's canonical text and digest have one owner, so a proof the agent signs and a command the module signs are proved by the same rule in both languages.
          • The module now asks the camera host that holds the camera to make a recording, instead of pretending that a recording happened, and the host is told on its next turn.
          • The wallet's security gate now reads the database's real grants instead of believing them, and a missing grant closes the gate.
          • The committed model snapshot is now checked against the committed migrations, so a snapshot that has drifted is caught before it reaches a database.

        27. 1.5.1

          Released

          • The assistant now shows the model exactly how to call a tool, so a call reaches the tool it names instead of failing on a label.

        28. 1.5.0

          Released

          • Money can go back: a refund is a record of its own, an invoice and a credit note are real documents, and a tax that has not been configured issues no document at all.
          • The books can prove themselves: the reconciliation now reads the payment gateway's own settlement record, so a disagreement is found instead of counted.
          • A file can now be attached to a recording or to evidence, and it is kept only when the scan says it is clean.

        29. 1.4.0

          Released

          • A person can now ask the server who they are: their own address, their own state and their own devices - and they can end one of their own devices.
          • Every module now answers the same health question in the same shape, and the persistence, the configuration and the diagnostics each have one owner instead of several copies.
          • The web client's shared parts - the way a call leaves, the session, and the states a screen shows - live in one package now, so two screens cannot disagree about what a refusal says.

        30. 1.3.0

          Released

          • The routes now answer a refusal in the language the caller asked for, and the notification badge counts what the server says rather than what the browser counts.
          • A person can enrol their own device and an administrator can refuse it, and a refused device's sessions end at once.
          • The diagnostics now index every failure, keep their retention as configuration an operator can read, and refuse a write that would pass a declared budget.
          • Money can be collected in a sandbox - and only in a sandbox: the payment page asks for no card detail, the notification is signed, and a forged one is never written down.

        31. 1.2.1

          Released

          • The landing on cam.pehromgroup.com is the surveillance product's own page again; the unlisted-share landing moves to the market module's own domain, market.pehromgroup.com.

        32. 1.0.0

          Released

          • One premium component library now serves the web, Android and desktop apps: a shared shell, person menu, page header, fields, buttons, banners, state views and panels, with generated design tokens; the screens moved onto it and the duplicate interface code was deleted.
          • A refused sign-in on the web and Android now clears both fields, so the address can be corrected without retyping the password.
          • The wallet security gate is closed: the ledger is append-only, every journal entry is linked, the 13-test security matrix passes, and the module and core suites pass with the database isolation bracket unchanged.
          • Uploads can be cancelled, recover after a crash, sweep abandoned staging files without starving a live upload, and reserve storage quota one writer at a time.

      • Web

        1. 1.9.27

          Released

          • The surveillance workspace now names its KYC review desk, and the reviewer permission is granted by the role seed.
          • Reviewers reach the queue and profile decisions; ordinary accounts are refused, and own KYC stays separate.

        2. 1.9.26

          Released

          • Declared form-group catalogue prices, the refund admin queue and buyer wording, and the showcase control entrance.

        3. 1.9.20

          Released

          • The shared landing footer keeps the caveat, tagline and links inside the brand column at 320px and 200% text, so the phone page no longer widens. The footer caveat remains part of the footer rather than a white strip above it.

        4. 1.9.18

          Released

          • The module's honest caveat now sits inside the footer under the product line, instead of a separate white strip between the sign-in band and the footer. The footer and the caveat are one surface, and the old standalone footnote is gone from every shared landing page.

        5. 1.9.17

          Released

          • The shared live player uses the HLS engine where available so the media token is sent as an Authorization header on every stream request; the native fallback stays for browsers without that engine.

        6. 1.9.16

          Released

          • The Billing accounts screen keeps the provider verification result after the check, instead of replacing it with the previous unverified list row.

        7. 1.9.15

          Released

          • The recurring mandate now ends inside the provider's 30-year validity instead of asking for 100 years, so UPI Autopay and card authorisation can complete.

        8. 1.9.14

          Released

          • A safe Billing accounts screen lists each configured payment connection with its provider, mode, approval, plan and webhook readiness, and a Verify button that checks the provider plan. It has no field for a key or a secret.

        9. 1.9.13

          Released

          • A billing account whose provider or domain approval is pending or suspended no longer receives a gateway, so it cannot open a checkout or accept a notification. The safe account list names the approval state.

        10. 1.9.12

          Released

          • Administrators can list the configured billing accounts and check an account's plan with its provider. The answer states only safe facts - whether a plan or webhook secret is present and whether the provider accepted the check - and never returns a key id or a secret.

        11. 1.9.11

          Released

          • The release history now shows each release's exact India time beside its date in both languages; the shared landing package is rebuilt before the client so the deployed page carries the change.

        12. 1.9.10

          Released

          • Every release in the version history now shows the exact India time beside its date, in both English and Hindi, so two releases on the same day can be told apart.

        13. 1.9.9

          Released

          • Billing accounts now own their gateway connection and webhook signature, so a second account cannot act through the platform account.
          • A subscription, its charges and its payment events now carry the billing account that owns them, and a verified notification cannot change another account's subscription.

        14. 1.9.6

          Released

          • The refund ground is now a required closed set: a refund is accepted only for a duplicate charge, a service that was never delivered, or a charge taken after a cancellation. The server refuses any other reason and the existing refusal shape is unchanged.
          • The detection-zone dialog, the upload page and the camera-consent dialog now use the shared form page and field owners, with numbered sections, an error summary, the module's own refusal and a server-confirmed result.

        15. 1.9.5

          Released

          • Email-code sign-in is live: the shared sign-in form offers a password or an email code, with separate accessible hints for the address and the code, a server-stated code length and resend wait, a generic answer for every address, and the same session handoff as the password route. Password sign-in is unchanged.

        16. 1.9.3

          Released

          • Email OTP server, the subscription buyer screens, OpenRouter free-model AI routing and the latest surveillance form/list screens are included. Email OTP sign-in screen is not yet part of this release; password sign-in is unchanged.

        17. 1.9.2

          Released

          • Security-layer and billing maintenance: the tenant-scoped billing subscription schema is in place, and the server-side Razorpay integration is included but disabled until configured. No price is charged.

        18. 1.9.1

          Released

          • Core scheduler retention duties, fail-closed tenant policies, the bounded diagnostics ingest and the shared form-owner screens are deployed.

        19. 1.9.0

          Released

          • The module resolves its tenant from the request host before sign-in, and the tenant's stored brand, display name, support contact and colour roles are painted on its own sign-in and workspace pages. Tenant administration, invitations, the catalogue with plans and orders, entitlements, export and deletion are part of the release, and row-level isolation fails closed instead of falling open to the platform tenant.
          • Twenty more surveillance screens are declared once in the module's form contract and render through the shared field, selector and button owners. Sign-in asks for a second factor only when the server says one is required, and the account list states whether each account holds an active factor.
          • App-lock and attestation challenges are connected to the sign-in chain, so a locked app does not open without the server's verification. The surveillance media chain keeps one gap-free recording timeline under concurrent appends, and a recording still missing its upload after 24 hours becomes Failed with RecordingUnavailable instead of Complete.
          • The web and native clients carry the 320px and 1280px navigation, brand and read-frame fixes, and the public landing offers Android 0.1.2 for both phone processors: arm64-v8a at 15,094,074 bytes and armeabi-v7a at 9,620,390 bytes, each with its checksum.

        20. 1.8.5

          Released

          • The surveillance module resolves its tenant from the request host before sign-in: an unknown host answers 404, a suspended tenant 403 and an archived tenant 410, and a tenant cannot be chosen by a request header.
          • The tenant directory is the module's own: six management routes and one public read, two permissions, and row-level isolation in the module's own database. The platform tenant answers on cam.pehromgroup.com and on the loopback addresses this machine's clients use.
          • The NAS recordings browser and player are live: configurable SMB or folder sources, range streaming, H.264 playback, H.265 transcoding, thumbnails and download, in English and Hindi at 320px.

        21. 1.8.3

          Released

          • The surveillance server publishes the report and layout kinds, revokes an older share link by id, names the release state and labels, enforces two-person approval, publishes integration kinds, the storage policy and attachable uploads, and records camera-host capabilities.

        22. 1.8.2

          Released

          • The workspace gains the video wall, notification preferences and the upload screen, and the web client now uses the one generated frame with no duplicated keys.

        23. 1.8.1

          Released

          • The workspace gains a self/device camera: the camera on the machine you are using can be previewed live, with its own permission and a release when you stop or leave. No recording and no upload.
          • The reset screen and its mail configuration are carried in the same release.

        24. 1.8.0

          Released

          • The surveillance catalogue reads answer from the module own rules: alert event kinds, location node kinds, analytics rule kinds, camera command kinds, privacy mask effects, maintenance windows, investigation owners, upload options and storage coverage.
          • A maintenance window now has a real end beside its promised end, and the billing seed follows the permission catalogue so the seeded roles hold every permission again.
          • The password-reset mail is configured with the domain sender, and a bilingual reset screen accepts the link and sets the new password.

        25. 1.7.0

          Released

          • The camera's own machine now drives the camera: the agent opens it, learns what it is and what it can do, reads its streams, steers it, reads its presets and its firmware, and starts and stops its recording. The camera's own credential stays on the camera's machine.
          • The module now publishes a signed release for a camera host to take, and the host learns of a recording to make on its next poll: the module asks, the host makes it, and the module records what became of it.
          • The protocol's own wording has one owner in both languages, so the module that signs a release and the host that verifies it cover the same bytes - which is why the engine's contract moved from version 2 to version 3 and a module on the old library now refuses to start.

        26. 1.6.0

          Released

          • The camera's own machine now runs an agent that answers for it: the protocol's canonical text and digest have one owner, so a proof the agent signs and a command the module signs are proved by the same rule in both languages.
          • The module now asks the camera host that holds the camera to make a recording, instead of pretending that a recording happened, and the host is told on its next turn.
          • The wallet's security gate now reads the database's real grants instead of believing them, and a missing grant closes the gate.
          • The committed model snapshot is now checked against the committed migrations, so a snapshot that has drifted is caught before it reaches a database.

        27. 1.5.1

          Released

          • The assistant now shows the model exactly how to call a tool, so a call reaches the tool it names instead of failing on a label.

        28. 1.5.0

          Released

          • Money can go back: a refund is a record of its own, an invoice and a credit note are real documents, and a tax that has not been configured issues no document at all.
          • The books can prove themselves: the reconciliation now reads the payment gateway's own settlement record, so a disagreement is found instead of counted.
          • A file can now be attached to a recording or to evidence, and it is kept only when the scan says it is clean.

        29. 1.4.0

          Released

          • A person can now ask the server who they are: their own address, their own state and their own devices - and they can end one of their own devices.
          • Every module now answers the same health question in the same shape, and the persistence, the configuration and the diagnostics each have one owner instead of several copies.
          • The web client's shared parts - the way a call leaves, the session, and the states a screen shows - live in one package now, so two screens cannot disagree about what a refusal says.

        30. 1.3.0

          Released

          • The routes now answer a refusal in the language the caller asked for, and the notification badge counts what the server says rather than what the browser counts.
          • A person can enrol their own device and an administrator can refuse it, and a refused device's sessions end at once.
          • The diagnostics now index every failure, keep their retention as configuration an operator can read, and refuse a write that would pass a declared budget.
          • Money can be collected in a sandbox - and only in a sandbox: the payment page asks for no card detail, the notification is signed, and a forged one is never written down.

        31. 1.2.1

          Released

          • The landing on cam.pehromgroup.com is the surveillance product's own page again; the unlisted-share landing moves to the market module's own domain, market.pehromgroup.com.

        32. 1.0.0

          Released

          • One premium component library now serves the web, Android and desktop apps: a shared shell, person menu, page header, fields, buttons, banners, state views and panels, with generated design tokens; the screens moved onto it and the duplicate interface code was deleted.
          • A refused sign-in on the web and Android now clears both fields, so the address can be corrected without retyping the password.
          • The wallet security gate is closed: the ledger is append-only, every journal entry is linked, the 13-test security matrix passes, and the module and core suites pass with the database isolation bracket unchanged.
          • Uploads can be cancelled, recover after a crash, sweep abandoned staging files without starving a live upload, and reserve storage quota one writer at a time.

      • Android

        Android app

        The native app for Android phones and tablets, signed with the product release key. Download the package directly; no store account is needed.

        1. 0.1.2

          Released

          • Live talk reaches a camera: the phone opens a talk session, sends its microphone to the camera over WebRTC, and offers mute, hold and close. The audio peer joins only when a camera host answers; when none does, the session says so instead of pretending it is connected.
          • The Android download is now one package per phone processor: a 32-bit phone downloads the 9.6 MB package built for it, and a newer 64-bit phone the 15.1 MB one, instead of every phone carrying every processor's native libraries.
          • Events are on the phone: the list shows what happened at each camera, and a person can acknowledge an event and then resolve it, with the server recording each step.
          • Camera care is on the phone: a saved position is written to the camera's own preset list, and a movement command is refused in words when the camera has never answered.
          • Sharing is on the phone: a share link is created and shown once, access is granted to an address, and a zone can be switched on or off, all against the module's own rules.
          • The video wall and viewer layouts are on the phone: a display opens its tiles into a real viewing session, and a layout can be created or edited and saved.
          • Patrol and reports are on the phone: a run starts, an observation is added, the run completes, and a report runs on the server from the phone.

        2. 0.1.1

          Released

          • The Android package is rebuilt from a changed native version input, proving that one native change produces a new published version, a new signed file and a new permanent download address.

        3. 0.1.0

          Released

          • The first signed Android build of the product is published: the native app for phones and tablets, with the existing camera slice, sign-in and the bilingual shell.

      • Desktop

        Windows desktop app

        The native app for Windows. Download the package, unpack it, and start the app; the Windows runtime and UI toolkit are used from the machine rather than carried a second time.

        1. 1.0.0

          Released

          • The first Windows desktop build of the product is published: the native WinUI app with sign-in, the shared shell and the camera list.

      Hear when a share or a price is published

      Leave your email address and the business will write to you about the shares it lists and the prices it publishes. It sends no tips and promises no returns.

      One mail a day about the shares this business offers. Every mail carries a way to stop them.

      The address we should write to, such as name@example.com.