Clear commercial and technical answers
Know what you are buying, building, and operating.
These answers explain how Starlife separates products, custom work, deployment, hosting, licensing, ownership, support, and change requests.
Products & licensing
Buying and evaluating Starlife products
What is the difference between a product and custom software?
A product has an existing, defined feature set and commercial path. Custom software is designed around a unique workflow after discovery and written scope. A product may still be configured or extended, but those changes are separate from the standard product.
Is WhaChat a real Starlife product?
Yes. WhaChat is Starlife Technologies' customer-support platform. It includes a website widget, owner and agent workspaces, live messaging, routing, visitor intelligence, status stories, tickets, notifications, analytics, and SaaS account foundations.
Can I see a demo before making a commercial decision?
Yes. A business demo is arranged around the features relevant to your team, websites, support workflow, and deployment needs. Demo access does not transfer a production license or ownership.
Can a product be white-labeled or resold?
Only where a written commercial license explicitly permits it. Standard hosted access or installation does not automatically include resale, source redistribution, brand removal, sublicensing, or unlimited deployments.
Why are some catalog entries called packages?
They are structured services, not pretend downloadable products. A package defines a common delivery path, but the final scope still depends on the client's content, infrastructure, integrations, and requirements.
Projects & delivery
Scope, timing, payment, and ownership
How does a custom project begin?
It begins with discovery. We define users, workflows, data, permissions, integrations, infrastructure, timeline, and success criteria. Starlife then prepares the suitable scope, milestones, responsibilities, and commercial terms.
How long does development take?
Timing depends on uncertainty, scope, integrations, content, approvals, migration, and testing. A focused website may take weeks; a multi-role SaaS platform may require staged delivery over months. We provide a timeline only after understanding the actual work.
How are payments structured?
Products, packages, milestone projects, and care plans have different payment structures. The written offer states currency, schedule, taxes or fees where applicable, what activates work, and what is due before production handover.
Who owns custom project work?
Ownership and usage rights are defined in the project agreement. Third-party libraries, licensed assets, commercial products, hosting accounts, and reusable Starlife components retain their own terms. Final transfer depends on full payment and the written agreement.
Can requirements change during development?
Yes, but a change may affect cost, timeline, architecture, testing, and earlier work. We document material changes and confirm their impact instead of silently adding them to the original scope.
Installation & hosting
Production readiness
Does buying software include installation?
Not automatically. A software license and a managed installation are different commercial items unless the offer bundles them. Installation covers environment setup, database, storage, domain, SSL, email, routes, verification, and handover as applicable.
Can Starlife deploy on my existing hosting?
Yes, if the environment satisfies the software requirements and provides sufficient access. We may recommend an upgrade or migration if runtime, memory, process, storage, database, SSL, email, or management limits create production risk.
Does Starlife only use MilesWeb?
No. MilesWeb is a hosting partner and a familiar platform, but recommendations should follow the application's needs. We can assess other cPanel, cloud, VPS, or dedicated environments where access and support are suitable.
What should I provide for installation?
Valid software ownership or license, hosting or server access, domain and DNS control, database and email details or permission to create them, required third-party credentials, documentation, and an available decision-maker for final verification.
Support & security
After launch
What happens after a project goes live?
Handover includes the agreed access, deployment record, training or guidance, and warranty or support terms. Ongoing updates, monitoring, incident response, minor changes, and infrastructure care can be covered through a managed plan.
Is every reported issue a free bug fix?
No. We first identify whether the issue is a defect against agreed scope, an environment or third-party failure, unsupported modification, user-operation issue, expired support item, or a new requirement. The correct route is confirmed before work.
How should I report a security concern?
Use the contact or support channel, state that it is a security concern, and provide only the minimum safe evidence. Do not publish exploit details or send passwords, private keys, personal data, payment data, or full database exports through public chat.
Can Starlife recover a failed deployment?
Often, provided the current files, logs, environment, and last working backup are preserved. Avoid repeated destructive uploads or resets. Share the error, timeline, host, and last change so we can assess the failure safely.
Your question is specific to your business
Bring the context and get an answer that can guide a decision.
We can discuss the product, implementation, custom build, infrastructure, licensing, or support route that applies.