Customize Login Page

Feature Requests
1

I would like to raise an important concern regarding the current authentication system.

Most professional software platforms, including banks, financial institutions, government portals, and enterprise applications, allow users to access their dashboards using a secure User ID and Password login system. Even government organizations such as the West Bengal State Electricity Distribution Company Limited (WBSEDCL) provide dashboard access through standard username and password authentication.

However, your platform currently relies on Heracles Authentication as the primary login method, without providing developers the option to implement a traditional User ID and Password login. In my opinion, this approach is restrictive and makes enterprise software appear less professional, especially for organizations that require familiar authentication methods for employees, administrators, and customers.

As software developers, we invest significant time, effort, and financial resources into building enterprise-grade applications using your AI services. Many of these projects involve substantial investments, and it becomes difficult when the authentication flow is limited to a single mandatory method.

I respectfully request that you introduce an option allowing developers to implement a standard User ID and Password authentication system without requiring Heracles Authentication. This would provide greater flexibility and make your platform more suitable for professional software development, particularly for banking, fintech, government, and other enterprise applications.

Providing developers with multiple authentication options would improve usability, increase adoption, and better meet the requirements of real-world enterprise software.

Thank you for considering this feedback. I hope you will introduce this feature in a future update.

2 Likes
2

Hello,

Thank you for sharing this detailed feedback. I understand why having a traditional User ID and Password option would feel important for enterprise, banking, fintech, government, and internal business applications.

At the moment, Hercules does not offer a separate developer-controlled username and password authentication option in the way you described.

We really appreciate you taking the time to explain the use case and why it matters for professional software development.

Best,
Crystal
The Hercules Team

3

Hello Nabab,

We already support email and password login, and you can enable it alongside (or instead of) social sign-in methods.

To set it up:

  1. Go to Branding & SEO → Customize Auth Portal.
  2. Under Sign-in Methods, turn on Email and password.
  3. Save your changes.

Your users will then see a “Continue with email & password” option on your Auth Portal. You can also toggle other methods (Google, Apple, etc.) on or off there, so you can show only email and password if you prefer.

If this doesn’t fit your needs, can you let us know more details about the type of username password setup you are looking for?

4

Hello, can you let us know why email + password auth doesn’t work for you? Is there reasons like privacy, more control or anything else?

5

Thank you for the feedback. We are building id + password login and expect to have it ready in the next week or two.

6

Hello,

We have released an update to add a user id + password login option. You can find this under “Branding & SEO” > “Customize Auth Portal”. Let us know how it goes.

7

Screenshot 2026-07-14 230354
Screenshot 2026-07-14 2303541907×837 90.5 KB

Authentication Should Be Fully Prompt-Driven

After reviewing the current implementation, I noticed that the Sign-In Method still requires developers or administrators to manually select or configure authentication options before the login system becomes functional.

From an enterprise software architecture perspective, this is not the expected behavior.

Since the entire application is being generated through AI-defined prompts, the authentication workflow should also be generated automatically based on those prompts.

For example, if the prompt specifies:

  • An Admin Login page with predefined credentials.
  • A Staff Login portal where credentials are assigned by the Administrator.
  • A Customer Registration page where users create their own username and password.
  • A Sub-Admin login with predefined roles and permissions.

Then the system should automatically generate the complete authentication architecture accordingly.

There should be no requirement to manually select a Sign-In Method or manually configure authentication settings after the application has been generated.

The AI prompt should define:

  • Authentication type
  • Login pages
  • User roles
  • User provisioning logic
  • Credential generation
  • Password policies
  • Role-based permissions
  • Authentication workflows

Based on these prompt definitions, the system should automatically create the required database structures, authentication services, identity records, and server-side configuration.

The authentication engine should simply verify the credentials that have already been created automatically by the application’s business logic.

In other words, authentication should be prompt-driven, not manually configured after software generation.

The desired workflow should be:

AI Prompt
      │
      ▼
Generate Software Architecture
      │
      ▼
Generate Authentication Configuration
      │
      ▼
Create Database Schema
      │
      ▼
Create Default Users (if defined)
      │
      ▼
Configure Roles & Permissions
      │
      ▼
Deploy Application
      │
      ▼
Users Can Sign In Immediately

At no stage should a developer or administrator be required to manually configure authentication options through the Sign-In Method page if those requirements have already been defined in the AI prompt.

This is the expected behavior for an AI-driven application generation platform and aligns with modern enterprise software development practices.

Thank you

Nabab