PUBLIC DESIGN PREVIEW—A new home for your studio.Payments are not live.
NSSTUDIO OS
FOR YOUR EVERYDAY
Explore NS
Admin

A CONNECTED BUSINESS. LOCAL CUSTOMER WORK.

Your studio works here.
Your account connects it.

The website manages the business relationship. The desktop keeps customer records, photos and everyday work on your computer. A secure API connects only the permitted account and device information.

On your computer

Customers, events, balances, original photos, local AI, Copy Manager, delivery and verified records backups.

The secure connection

HTTPS, one-time device proof and signed permission. No direct access to either database from the other app.

In your website account

Subscription information, registered devices, verified payment references, support, tutorials and chosen message preferences.

YOUR FIRST USEFUL RESULT

Seven simple steps.
Choose what you need.

This is an optional learning journey, not seven activation locks. You do not need to create fake bookings, payments or messages to finish setup.

  1. 01

    Set up your studio

    Choose your studio name, language, PIN and backup location.

    See the walkthrough
  2. 02

    Save a customer number

    Start with a phone number. Add a name later and ask before enabling messages.

    See the walkthrough
  3. 03

    Record a real booking

    Keep the event date, agreed amount and advance separate. No real booking yet? Skip this step.

    See the walkthrough
  4. 04

    Verify a file copy

    Try copied test files in Copy Manager and check the verification result.

    See the walkthrough
  5. 05

    Record money received

    Record only actual payments. Delivery and completion do not erase a balance.

    See the walkthrough
  6. 06

    Prepare a useful message

    Choose a consenting customer, review the draft and send it yourself.

    See the walkthrough
  7. 07

    Try one photo tool

    Work on a separate copy and check the result. Photo tools are the extra bonus.

    See the walkthrough

Activation is not daily payment

The proposed monthly plan remains ₹99. A short-lived permission proves access for one registered computer; refreshing that permission does not charge the customer again.

The current owner installer is unchanged and unlicensed. The website connection is a separate test. Commercial protection, signed distribution and final offline-grace rules still require release approval.

Open my account

PRACTICAL PROTECTION

Seven protection groups.
One fair promise.

Make copying harder without punishing genuine customers. No desktop app can honestly promise impossible-to-break protection.

Seven groups organise eight technical controls. Each status below describes its actual stage, not a piracy-proof claim.

  1. 01

    Account ownership

    Private account actions require sign-in. Owner actions are checked separately.

    Implemented in preview
  2. 02

    Subscription authority

    Only verified provider evidence or an explicit owner test grant can create access. Browser success text is not payment proof.

    Test mode only
  3. 03

    Registered computer

    A random installation key identifies the device. Customer photos, phone numbers and hardware serials are not used as an activation key.

    Implemented in preview
  4. 04

    Signed permission

    The server signs a short-lived, device-bound permission. The app has a public verification key, never the signing secret.

    Test mode only
  5. 05

    Protected offline cache

    A valid cached permission can be checked without internet. Windows account protection is not a hardware dongle or a guarantee against same-user malware.

    Desktop source tested
  6. 06

    Renewal, revocation and recovery

    Explicit online refresh checks the registered device. A network failure does not erase an existing cached permission or studio records.

    Test connection

    Revocation blocks future permission renewal. Already-issued offline permission lasts until expiry; replacement needs account ownership checks.

    Recovery policy pending
  7. 07

    Signed distribution

    A publisher-signed installer, verified updates and staged rollout are required before protected commercial distribution. A checksum alone is not publisher trust.

    Launch requirement

A licence expiry must never delete customer history, photos or backups. Existing authenticated record access and safe completion of running jobs are protected.

Helpful connection, never silent surveillance

Automatic usage telemetry is off. Device connection does not prove meaningful app use. We will not upload customer photos, names, balances or local backup paths to fill a website dashboard.

Future analytics need a separate opt-in, a small reviewed event list and a non-blocking offline queue. Messaging consent is not analytics consent.